How severe is CVE-2016-9391?

CVE-2016-9391 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2016-9391 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-9391?

CVE-2016-9391 affects Jasper Project Jasper. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2016-9391?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-9391 published?

CVE-2016-9391 was published on 2017-03-23 and last updated on 2026-06-17.

CVE-2016-9391

CVE-2016-9391 is a high-severity vulnerability in Jasper Project Jasper with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jasper Project Jasper
Published: 2017-03-23
Last modified: 2026-06-17

Description

The jpc_bitstream_getbits function in jpc_bs.c in JasPer before 2.0.10 allows remote attackers to cause a denial of service (assertion failure) via a very large integer.

Frequently asked questions

What is CVE-2016-9391?: The jpc_bitstream_getbits function in jpc_bs.c in JasPer before 2.0.10 allows remote attackers to cause a denial of service (assertion failure) via a very large integer.
How severe is CVE-2016-9391?: CVE-2016-9391 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2016-9391 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-9391?: CVE-2016-9391 affects Jasper Project Jasper. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-9391?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-9391 published?: CVE-2016-9391 was published on 2017-03-23 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:jasper_project:jasper:*:*:*:*:*:*:*:*

More vulnerabilities in Jasper Project Jasper

CVE-2008-3522 — Critical (CVSS 10.0): Buffer overflow in the jas_stream_printf function in libjasper/base/jas_stream.c in JasPer 1.900.1 might allow…
CVE-2008-3520 — Critical (CVSS 9.3): Multiple integer overflows in JasPer 1.900.1 might allow context-dependent attackers to have an unknown impact via a…
CVE-2015-8751 — High (CVSS 8.8): Integer overflow in the jas_matrix_create function in JasPer allows context-dependent attackers to have unspecified…
CVE-2018-19541 — High (CVSS 8.8): An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15,…
CVE-2018-19540 — High (CVSS 8.8): An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15,…
CVE-2023-51257 — High (CVSS 7.8): An invalid memory write issue in Jasper-Software Jasper v.4.1.1 and before allows a local attacker to execute arbitrary…

All CVEs affecting Jasper Project Jasper →