An out-of-bounds heap read vulnerability was found in jpc_pi_nextpcrl() function of jasper when processing crafted input. Upstream bug: https://github.com/mdadams/jasper/issues/103 Upstream patch: https://github.com/mdadams/jasper/commit/99a50593254d1b53002719bbecfc946c84b23d27 Acknowledgments: Name: Liu Bingchang (IIE)
Created mingw-jasper tracking bugs for this issue: Affects: fedora-all [bug 1405150] Affects: epel-7 [bug 1405152]
Created jasper tracking bugs for this issue: Affects: fedora-all [bug 1405149] Affects: epel-5 [bug 1405151]
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: https://github.com/mdadams/jasper/commit/aa0b0f79ade5eef8b0e7a214c03f5af54b36ba7d 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): https://github.com/mdadams/jasper/commit/f25486c3d4aa472fec79150f2c41ed4333395d3d These commits were apparently triggered by this upstream bug: https://github.com/mdadams/jasper/issues/94 This upstream bug: https://github.com/mdadams/jasper/issues/103 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): https://github.com/mdadams/jasper/commit/99a50593254d1b53002719bbecfc946c84b23d27 This fix was included in upstream jasper version 2.0.6.
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