An assertion test was used when ensuring the component domains are the same for the ICT/RCT in the JPC codec. Upstream patch: https://github.com/mdadams/jasper/commit/dee11ec440d7908d1daf69f40a3324b27cf213ba 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 information from the advisory: Affected version: 1.900.13 Output/failure: imginfo: /tmp/portage/media-libs/jasper-1.900.13/work/jasper-1.900.13/src/libjasper/jpc/jpc_mct.c:146: void jpc_irct(jas_matrix_t *, jas_matrix_t *, jas_matrix_t *): Assertion `((c1)->numrows_) == numrows && ((c1)->numcols_) == numcols && ((c2)->numrows_) == numrows && ((c2)->numcols_) == numcols’ failed. Commit fix: https://github.com/mdadams/jasper/commit/dee11ec440d7908d1daf69f40a3324b27cf213ba Fixed version: 1.900.14 Testcase: https://github.com/asarubbo/poc/blob/master/00006-jasper-assert-jpc_irct CVE: CVE-2016-9389 Upstream bug report: https://github.com/mdadams/jasper/issues/52
Another upstream report for different symptoms of the same problem: https://github.com/mdadams/jasper/issues/55 Reproducer: https://github.com/asarubbo/poc/blob/master/00009-jasper-assert-jpc_iict
Impact of this problem is limited to unexpected application termination. There is currently no plan to backport the fix to already released Red Hat Enterprise Linux versions.
Re-considering inclusion for easier future testing.
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