Bug 1488965 (CVE-2017-13752) - CVE-2017-13752 jasper: reachable assertion in jpc_dequantize()
Summary: CVE-2017-13752 jasper: reachable assertion in jpc_dequantize()
Status: NEW
Alias: CVE-2017-13752
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=low,public=20170825,reported=2...
Keywords: Security
Depends On: 1434464 1434465 1485276 1434467
Blocks: 1449402
TreeView+ depends on / blocked
 
Reported: 2017-09-06 14:01 UTC by Andrej Nemec
Modified: 2019-06-08 22:18 UTC (History)
15 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)

Description Andrej Nemec 2017-09-06 14:01:28 UTC
There is a reachable assertion abort in the function jpc_dequantize() in jpc/jpc_dec.c in JasPer 2.0.12 that will lead to a denial of service attack.

Product bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1485276

Comment 1 Andrej Nemec 2017-09-06 14:06:45 UTC
Created jasper tracking bugs for this issue:

Affects: fedora-all [bug 1434464]


Created mingw-jasper tracking bugs for this issue:

Affects: epel-7 [bug 1434465]
Affects: fedora-all [bug 1434467]

Comment 2 Agostino Sarubbo 2017-09-06 14:37:02 UTC
hi, mostly of the recent open bugs about jasper are duplicate of this:
https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure/

Comment 3 Andrej Nemec 2017-09-06 14:40:27 UTC
(In reply to Agostino Sarubbo from comment #2)
> hi, mostly of the recent open bugs about jasper are duplicate of this:
> https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure/

Hello Agostino,

Thanks, I caught that from your post to oss-security as well. I'll duplicate them as soon as Mitre lets us know, as that's the most reliable process for us.

Comment 4 Tomas Hoger 2017-12-05 12:21:31 UTC
This CVE is for the same reachable assertion as CVE-2016-9397 (bug 1396979).  Upstream bug report is:

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

The issue remains unfixed in the current upstream version 2.0.14.


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