7.5
Advisory Published
CVE Published
Updated

CVE-2016-9396

First published: Mon Nov 21 2016(Updated: )

An assertion failure was possible to trigger in JPC_NOMINALGAIN. 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 SoftwareAffected VersionHow to fix
debian/jasper
redhat/jasper<2.0.15
2.0.15
Jasper Reports<=1.900.11

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

Frequently Asked Questions

  • What is the severity of CVE-2016-9396?

    CVE-2016-9396 has a medium severity rating due to an assertion failure that can be exploited by remote attackers.

  • How do I fix CVE-2016-9396?

    To fix CVE-2016-9396, upgrade the JasPer package to version 2.0.15 or later.

  • Which versions of JasPer are affected by CVE-2016-9396?

    Versions of JasPer prior to 2.0.15 are affected by CVE-2016-9396.

  • Is CVE-2016-9396 an exploitable vulnerability?

    Yes, CVE-2016-9396 is considered exploitable as it allows remote attackers to trigger an assertion failure.

  • What component of JasPer is impacted by CVE-2016-9396?

    CVE-2016-9396 impacts the JPC_NOMINALGAIN function in jasper's jpc_t1cod.c file.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203