An assertion failure was possible to trigger in JPC_NOMINALGAIN. CVE assignment: http://seclists.org/oss-sec/2016/q4/441
Created mingw-jasper tracking bugs for this issue: Affects: fedora-all [bug 1396987] Affects: epel-7 [bug 1396989]
Created jasper tracking bugs for this issue: Affects: fedora-all [bug 1396986] Affects: epel-5 [bug 1396988]
Original reporter's advisory: https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure/ Relevant part of the advisory: Affected version: 1.900.13 Output/failure: /tmp/portage/media-libs/jasper-1.900.13/work/jasper-1.900.13/src/libjasper/jpc/jpc_t1cod.c:144: int JPC_NOMINALGAIN(int, int, int, int): Assertion `qmfbid == 0x01′ failed. Commit fix: N/A Fixed version: N/A Testcase: https://github.com/asarubbo/poc/blob/master/00004-jasper-assert-JPC_NOMINALGAIN CVE: CVE-2016-9396 Upstream bug report: https://github.com/mdadams/jasper/issues/50 This issue is still not fixed in the current upstream git, i.e. not fixed in the latest tagged version 2.0.4.
Remains unfixed in 2.0.11.
Fixed now upstream via: https://github.com/mdadams/jasper/commit/a10536d5f7f3164b0a1f1ae3e533f4a12ca6f543 Should be included in the next release, which presumably is going to be 2.0.15.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:3253 https://access.redhat.com/errata/RHSA-2018:3253