blob: 76cd5bb6cd999c50e990109f77e35b915e9a2f5c [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<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.
<product type="ebuild">JasPer</product>
<announced>January 23, 2012</announced>
<revised>January 23, 2012: 1</revised>
<package name="media-libs/jasper" auto="yes" arch="*">
<unaffected range="ge">1.900.1-r4</unaffected>
<vulnerable range="lt">1.900.1-r4</vulnerable>
<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>Two vulnerabilities have been found in JasPer:</p>
<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>The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c uses an
incorrect data type, possibly causing a heap-based buffer overflow
<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>There is no known workaround at this time.</p>
<p>All JasPer users should upgrade to the latest version:</p>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=media-libs/jasper-1.900.1-r4"
<uri link="">CVE-2011-4516</uri>
<uri link="">CVE-2011-4517</uri>
<metadata timestamp="Tue, 27 Dec 2011 05:22:50 +0000" tag="requester">
<metadata timestamp="Mon, 23 Jan 2012 19:50:54 +0000" tag="submitter">ackle</metadata>