Bug 1396967 (CVE-2016-9391)

Summary:	CVE-2016-9391 jasper: reachable assertions in the JPC bitstream code
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	abhgupta, bmcclain, cfergeau, dblechte, dmcphers, eedri, jialiu, jokerman, jridky, kseifried, lmeyer, lsurette, mgoldboi, michal.skrivanek, mmccomas, rbalakri, security-response-team, sherold, slawomir, srevivo, tiwillia, ykaul, ylavi
Target Milestone:	---	Keywords:	Reopened, Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	jasper 1.900.14	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-09 21:42:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1396986, 1396987, 1396988, 1396989, 1439171, 1439172, 1439173, 1439174
Bug Blocks:	1314477

Description Adam Mariš 2016-11-21 10:01:07 UTC

An assertion failure was used in JPC bitstream code when integer larger than what can be handled is requested.

Upstream patch:

https://github.com/mdadams/jasper/commit/1e84674d95353c64e5c4c0e7232ae86fd6ea813b

CVE assignment:

http://seclists.org/oss-sec/2016/q4/441

Comment 1 Adam Mariš 2016-11-21 10:33:29 UTC

Created mingw-jasper tracking bugs for this issue:

Affects: fedora-all [bug 1396987]
Affects: epel-7 [bug 1396989]

Comment 2 Adam Mariš 2016-11-21 10:33:46 UTC

Created jasper tracking bugs for this issue:

Affects: fedora-all [bug 1396986]
Affects: epel-5 [bug 1396988]

Comment 3 Tomas Hoger 2016-11-29 22:30:23 UTC

Original reporter's advisory:

https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure/

Upstream bug report:

https://github.com/mdadams/jasper/issues/59

Test case:

https://github.com/asarubbo/poc/blob/master/00014-jasper-assert-jpc_bitstream_getbits

Comment 5 Tomas Hoger 2016-11-29 22:37:05 UTC

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.

Comment 6 Tomas Hoger 2016-11-30 08:49:46 UTC

Quoting relevant part of the original reporter's advisory for posterity:

Affected version:
1.900.13

Output/failure:
type = 0xff05 (UNKNOWN); len = 20;01 40 40 00 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 imginfo: /tmp/portage/media-libs/jasper-1.900.13/work/jasper-1.900.13/src/libjasper/jpc/jpc_bs.c:197: long jpc_bitstream_getbits(jpc_bitstream_t *, int): Assertion `n >= 0 && n < 32' failed.

Commit fix:
https://github.com/mdadams/jasper/commit/1e84674d95353c64e5c4c0e7232ae86fd6ea813b

Fixed version:
1.900.14

Testcase:
https://github.com/asarubbo/poc/blob/master/00014-jasper-assert-jpc_bitstream_getbits

CVE:
CVE-2016-9391

Comment 7 Tomas Hoger 2017-03-31 21:04:54 UTC

Re-considering inclusion for easier future testing.

Comment 8 errata-xmlrpc 2017-05-09 17:19:43 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