First published: Fri Dec 16 2016(Updated: )
A use-after-free flaw was found in the way JasPer decoded certain JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash. Upstream issue (including a reproducer); <a href="https://github.com/mdadams/jasper/issues/105">https://github.com/mdadams/jasper/issues/105</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/jasper | ||
redhat/jasper | <2.0.12 | 2.0.12 |
Jasper Reports | <2.0.12 | |
redhat enterprise Linux desktop | =6.0 | |
redhat enterprise Linux desktop | =7.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux server | =7.0 | |
redhat enterprise Linux server eus | =7.3 | |
redhat enterprise Linux server eus | =7.4 | |
redhat enterprise Linux workstation | =6.0 | |
redhat enterprise Linux workstation | =7.0 | |
Debian GNU/Linux | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9591 has a medium severity rating due to its potential to cause application crashes.
To fix CVE-2016-9591, update the JasPer package to version 2.0.12 or later.
Versions prior to 2.0.12 of the JasPer package are affected by CVE-2016-9591.
Applications that utilize the JasPer library for JPEG 2000 decoding are vulnerable to CVE-2016-9591.
You can check your JasPer package version against the known affected versions to determine if your system is vulnerable to CVE-2016-9591.