Bug 1405148 (CVE-2016-9583) - CVE-2016-9583 jasper: integer overflows leading to out of bounds read in packet iterators in JPC decoder
Summary: CVE-2016-9583 jasper: integer overflows leading to out of bounds read in pack...
Alias: CVE-2016-9583
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1405149 1405150 1405151 1405152 1439171 1439172 1439173 1439174
Blocks: 1314477
TreeView+ depends on / blocked
Reported: 2016-12-15 17:06 UTC by Adam Mariš
Modified: 2019-09-29 14:02 UTC (History)
28 users (show)

Fixed In Version: jasper 2.0.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-05-09 21:40:26 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1208 normal SHIPPED_LIVE Important: jasper security update 2017-05-09 21:13:57 UTC

Description Adam Mariš 2016-12-15 17:06:04 UTC
An out-of-bounds heap read vulnerability was found in jpc_pi_nextpcrl() function of jasper when processing crafted input.

Upstream bug:


Upstream patch:



Name: Liu Bingchang (IIE)

Comment 1 Adam Mariš 2016-12-15 17:06:58 UTC
Created mingw-jasper tracking bugs for this issue:

Affects: fedora-all [bug 1405150]
Affects: epel-7 [bug 1405152]

Comment 2 Adam Mariš 2016-12-15 17:07:18 UTC
Created jasper tracking bugs for this issue:

Affects: fedora-all [bug 1405149]
Affects: epel-5 [bug 1405151]

Comment 4 Tomas Hoger 2017-03-30 21:29:24 UTC
The original problem was with integer overflows, which lead to out-of-bounds access.  That problem was originally addressed in jasper version 2.0.0 via this commit:


Shortly after the above commit, it was found that it introduced a bug into the jpc_pi_nextrpcl() function, which was corrected via this commit (still in version 2.0.0):


These commits were apparently triggered by this upstream bug:


This upstream bug:


reports similar issue to what was fixed in the jpc_pi_nextrpcl() function via f25486c, this time in the jpc_pi_nextpcrl() function.  This was corrected upstream via this commit (also linked in comment 0 above):


This fix was included in upstream jasper version 2.0.6.

Comment 5 errata-xmlrpc 2017-05-09 17:20:45 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

Via RHSA-2017:1208 https://access.redhat.com/errata/RHSA-2017:1208

Note You need to log in before you can comment on or make changes to this bug.