CVE-2016-9391
First published: Mon Nov 21 2016(Updated: )
An assertion failure was used in JPC bitstream code when integer larger than what can be handled is requested. Upstream patch: <a href="https://github.com/mdadams/jasper/commit/1e84674d95353c64e5c4c0e7232ae86fd6ea813b">https://github.com/mdadams/jasper/commit/1e84674d95353c64e5c4c0e7232ae86fd6ea813b</a> CVE assignment: <a href="http://seclists.org/oss-sec/2016/q4/441">http://seclists.org/oss-sec/2016/q4/441</a>
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/jasper | ||
| redhat/jasper | <1.900.14 | 1.900.14 |
| Jasper Reports | <=2.0.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.openwall.com/lists/oss-security/2016/11/17/1
- http://www.securityfocus.com/bid/94371
- https://access.redhat.com/errata/RHSA-2017:1208
- https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure
- https://bugzilla.redhat.com/show_bug.cgi?id=1396967
- https://github.com/mdadams/jasper/commit/1e84674d95353c64e5c4c0e7232ae86fd6ea813b
- https://usn.ubuntu.com/3693-1/
- https://launchpad.net/bugs/cve/CVE-2016-9391
- https://github.com/asarubbo/poc/blob/master/00014-jasper-assert-jpc_bitstream_getbits
- https://security-tracker.debian.org/tracker/CVE-2016-9391
- http://seclists.org/oss-sec/2016/q4/441
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1396987
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1396989
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1396986
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1396988
- https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure/
- https://github.com/mdadams/jasper/issues/59
- https://access.redhat.com/security/cve/CVE-2016-9391
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9391
- https://nvd.nist.gov/vuln/detail/CVE-2016-9391
- https://ubuntu.com/security/CVE-2016-9391
Frequently Asked Questions
What is the severity of CVE-2016-9391?
CVE-2016-9391 has a moderate severity rating, indicating it could potentially lead to application crashes.
How do I fix CVE-2016-9391?
To fix CVE-2016-9391, update to jasper version 1.900.14 or later.
What software is affected by CVE-2016-9391?
CVE-2016-9391 affects jasper versions prior to 1.900.14 on Red Hat and versions 2.0.6 and earlier on Jasper Reports.
What are the implications of CVE-2016-9391?
The implications of CVE-2016-9391 include potential application instability or crashes due to the assertion failure.
Is CVE-2016-9391 being actively exploited?
As of now, there are no publicly known exploits specifically targeting CVE-2016-9391.
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2016-9391
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/event
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/debian
- package-manager/redhat
- vendor/jasper project
- canonical/jasper reports
- version/jasper reports/2.0.6