metadata/glsa/glsa-201201-10.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201201-10">
  <title>JasPer: User-assisted execution of arbitrary code</title>
  <synopsis>Multiple memory management errors in JasPer could result in
    execution of arbitrary code or a Denial of Service.
  </synopsis>
  <product type="ebuild">JasPer</product>
  <announced>2012-01-23</announced>
  <revised count="1">2012-01-23</revised>
  <bug>394879</bug>
  <access>remote</access>
  <affected>
    <package name="media-libs/jasper" auto="yes" arch="*">
      <unaffected range="ge">1.900.1-r4</unaffected>
      <vulnerable range="lt">1.900.1-r4</vulnerable>
    </package>
  </affected>
  <background>
    <p>The JasPer Project is an open-source initiative to provide a free
      software-based reference implementation of the codec specified in the
      JPEG-2000 Part-1 (jpeg2k) standard.
    </p>
  </background>
  <description>
    <p>Two vulnerabilities have been found in JasPer:</p>
    
    <ul>
      <li>The jpc_cox_getcompparms function in libjasper/jpc/jpc_cs.c contains
        an error that could overwrite certain callback pointers, possibly
        causing a heap-based buffer overflow (CVE-2011-4516).
      </li>
      <li>The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c uses an
        incorrect data type, possibly causing a heap-based buffer overflow
        (CVE-2011-4517).
      </li>
    </ul>
  </description>
  <impact type="normal">
    <p>A remote attacker could entice a user or automated system to process
      specially crafted JPEG-2000 files with an application using JasPer,
      possibly resulting in the execution of arbitrary code with the privileges
      of the application, or a Denial of Service.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All JasPer users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=media-libs/jasper-1.900.1-r4"
    </code>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4516">CVE-2011-4516</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4517">CVE-2011-4517</uri>
  </references>
  <metadata timestamp="2011-12-27T05:22:50Z" tag="requester">
    underling
  </metadata>
  <metadata timestamp="2012-01-23T19:50:54Z" tag="submitter">ackle</metadata>
</glsa>