First published: Mon Nov 21 2016(Updated: )
An assertion failure was possible to trigger in jas_seq2d_create. Upstream patch: <a href="https://github.com/mdadams/jasper/commit/d42b2388f7f8e0332c846675133acea151fc557a">https://github.com/mdadams/jasper/commit/d42b2388f7f8e0332c846675133acea151fc557a</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 |
---|---|---|
redhat/jasper | <1.900.25 | 1.900.25 |
Jasper Reports | <=1.900.24 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9395 is classified as having a medium severity level due to the potential for an assertion failure.
To resolve CVE-2016-9395, upgrade to Jasper version 1.900.25 or later.
CVE-2016-9395 affects Jasper versions up to 1.900.24 and can be exploited in both the Jasper package from Red Hat and other installations.
CVE-2016-9395 is an assertion failure vulnerability that can be triggered in the jas_seq2d_create function.
You can check your Jasper software version and verify if it is earlier than 1.900.25 to determine vulnerability to CVE-2016-9395.