Bug 1416061 (CVE-2017-5499) - CVE-2017-5499 jasper: Signed integer overflow in jpc_dequantize() in jpc_dec.c
Summary: CVE-2017-5499 jasper: Signed integer overflow in jpc_dequantize() in jpc_dec.c
Alias: CVE-2017-5499
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1449402
TreeView+ depends on / blocked
Reported: 2017-01-24 13:58 UTC by Andrej Nemec
Modified: 2020-12-11 22:32 UTC (History)
19 users (show)

Fixed In Version: jasper 2.0.17
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-03-14 13:48:06 UTC

Attachments (Terms of Use)

Description Andrej Nemec 2017-01-24 13:58:54 UTC
A vulnerability was found in jasper. A crafted file could cause a signed integer overflow.



Comment 1 Tomas Hoger 2017-03-14 13:46:44 UTC
Upstream bug report:


This issue has not been resolved upstream yet (the current upstream version is 2.0.12).

Reporter's advisory:


Relevant information from the advisory:

With the undefined behavior sanitizer enabled, jasper crashes showing some left shift and some signed integer overflow.


Affected version / Tested on: 1.900.17
Fixed version: N/A
Commit fix: N/A

Relevant part of the stacktrace:

# imginfo -f $FILE
/tmp/portage/media-libs/jasper-1.900.17/work/jasper-1.900.17/src/libjasper/jpc/jpc_dec.c:1838:9: runtime error: signed integer overflow: -64356352 * 6359082673847140352 cannot be represented in type 'long'

CVE: CVE-2017-5499

Comment 2 Tomas Hoger 2017-03-14 13:48:06 UTC
The important information form the advisory is that this crash only occurs when jasper is compiles with undefined behaviour sanitizer (ubsan) enabled.  That is a development tool aimed to identify possible code bugs related to undefined behaviour.  There is no crash as described by this CVE in builds not using ubsan.

Comment 4 Tomas Hoger 2020-12-11 22:32:41 UTC
Upstream commit:


Fixed upstream in jasper 2.0.17.

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