CVE-2016-9387

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer overflow in the jpc_dec_process_siz function in libjasper/jpc/jpc_dec.c in JasPer before 1.900.13 allows remote attackers to have unspecified impact via a crafted file, which triggers an assertion failure.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 23, 2017

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Sep 29, 2026
Patch available. Sources: redhat, github_commit.
redhat Patch Available

Affected: Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:1208
generic

CVE-2016-9387 - PSIRT.COM

http://www.securityfocus.com/bid/94374
generic

oss-security - Re: jasper: multiple assertion failures

http://www.openwall.com/lists/oss-security/2016/11/17/1
github_commit Patch Available

commit d91198abd00f (mdadams/jasper)

Patch available: mdadams/jasper version-2.0.26 (contains commit d91198abd00f)

https://github.com/mdadams/jasper/commit/d91198abd00fc435a397fe6bad906a4c1748e9cf
redhat Patch Available

1396959 – (CVE-2016-9387) CVE-2016-9387 jasper: integer overflow in jpc_dec_process_siz()

Affected: Red Hat Enterprise Linux 6 and 7.

https://bugzilla.redhat.com/show_bug.cgi?id=1396959
generic

jasper: multiple Assertion failure | agostino's blog

https://blogs.gentoo.org/ago/2016/11/16/jasper-multiple-assertion-failure

Vendor Advisories for CVE-2016-9387(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjasper1 (1.900.1-debian1-2.4ubuntu1.2) @ xenial2026-05-22ubuntu
redhatjasper-0:1.900.1-30.el7_32017-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 160 total refreshes for this CVE.

  1. 2026-10-05 17:38 UTCEPSS rescore
  2. 2026-10-04 23:17 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-10-03 14:21 UTCEPSS rescore
  5. 2026-09-30 14:58 UTCEPSS rescore
  6. 2026-09-30 09:18 UTCEG score recompute
  7. 2026-09-28 13:45 UTCEPSS rescore
  8. 2026-09-27 13:40 UTCEPSS rescore
  9. 2026-09-26 15:53 UTCEPSS rescore
  10. 2026-09-26 15:53 UTCEPSS rescore
  11. 2026-09-24 13:59 UTCEPSS rescore
  12. 2026-09-23 13:41 UTCEPSS rescore
  13. 2026-09-20 20:09 UTCEPSS rescore
  14. 2026-09-19 15:35 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-18 14:20 UTCOSV refresh
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-16 05:05 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:41 UTCEPSS rescore
  21. 2026-09-12 14:55 UTCEPSS rescore
  22. 2026-09-11 14:46 UTCEPSS rescore
  23. 2026-09-11 09:31 UTCEPSS rescore
  24. 2026-09-10 09:26 UTCEPSS rescore
  25. 2026-09-07 15:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 13:56 UTCEPSS rescore
  2. 2026-09-02 14:07 UTCEPSS rescore
  3. 2026-09-01 13:48 UTCEPSS rescore
  4. 2026-09-01 03:31 UTCEPSS rescore
  5. 2026-08-30 16:51 UTCOSV refresh
  6. 2026-08-28 21:35 UTCEPSS rescore
  7. 2026-08-27 14:20 UTCEPSS rescore
  8. 2026-08-26 14:41 UTCEPSS rescore
  9. 2026-08-25 13:44 UTCEPSS rescore
  10. 2026-08-21 23:44 UTCEPSS rescore
  11. 2026-08-19 16:59 UTCEPSS rescore
  12. 2026-08-18 13:43 UTCEPSS rescore
  13. 2026-08-17 13:42 UTCEPSS rescore
  14. 2026-08-16 14:51 UTCEPSS rescore
  15. 2026-08-16 02:10 UTCEPSS rescore
  16. 2026-08-15 01:25 UTCEPSS rescore
  17. 2026-08-14 04:49 UTCOSV refresh
  18. 2026-08-12 13:46 UTCEPSS rescore
  19. 2026-08-11 13:36 UTCEPSS rescore
  20. 2026-08-08 16:32 UTCEPSS rescore
  21. 2026-08-07 16:22 UTCEPSS rescore
  22. 2026-08-06 13:42 UTCEPSS rescore
  23. 2026-08-05 19:12 UTCEPSS rescore
  24. 2026-08-04 15:05 UTCEPSS rescore
  25. 2026-08-02 02:22 UTCEPSS rescore
  26. 2026-08-01 04:11 UTCEPSS rescore
  27. 2026-07-30 16:24 UTCEPSS rescore
  28. 2026-07-30 01:26 UTCEPSS rescore
  29. 2026-07-30 01:26 UTCEPSS rescore
  30. 2026-07-29 09:07 UTCOSV refresh
  31. 2026-07-28 15:31 UTCEPSS rescore
  32. 2026-07-26 14:50 UTCEPSS rescore
  33. 2026-07-25 14:13 UTCEPSS rescore
  34. 2026-07-24 14:13 UTCEPSS rescore
  35. 2026-07-23 14:15 UTCEPSS rescore
  36. 2026-07-23 01:24 UTCEG score recompute
  37. 2026-07-22 22:04 UTCEG score recompute
  38. 2026-07-22 14:04 UTCEPSS rescore
  39. 2026-07-21 15:21 UTCEPSS rescore
  40. 2026-07-21 15:21 UTCEPSS rescore
  41. 2026-07-20 17:04 UTCEPSS rescore
  42. 2026-07-19 14:28 UTCEPSS rescore
  43. 2026-07-19 14:28 UTCEPSS rescore
  44. 2026-07-19 02:26 UTCEPSS rescore
  45. 2026-07-19 02:26 UTCEPSS rescore
  46. 2026-07-18 10:00 UTCEPSS rescore
  47. 2026-07-18 10:00 UTCEPSS rescore
  48. 2026-07-16 16:59 UTCEPSS rescore
  49. 2026-07-16 16:59 UTCEPSS rescore
  50. 2026-07-15 16:54 UTCEPSS rescore
  51. 2026-07-15 16:54 UTCEPSS rescore
  52. 2026-07-15 01:56 UTCEPSS rescore
  53. 2026-07-13 22:26 UTCEPSS rescore
  54. 2026-07-13 06:09 UTCEPSS rescore
  55. 2026-07-12 05:43 UTCEPSS rescore
  56. 2026-07-12 05:43 UTCEPSS rescore
  57. 2026-07-12 01:52 UTCOSV refresh
  58. 2026-07-11 08:24 UTCEPSS rescore
  59. 2026-07-09 19:06 UTCEPSS rescore
  60. 2026-07-08 15:10 UTCEPSS rescore
  61. 2026-07-07 13:42 UTCEPSS rescore
  62. 2026-07-06 16:24 UTCEPSS rescore
  63. 2026-07-06 16:24 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-06 02:20 UTCEPSS rescore
  66. 2026-07-05 02:27 UTCEPSS rescore
  67. 2026-07-04 06:28 UTCEPSS rescore
  68. 2026-07-01 15:02 UTCEPSS rescore
  69. 2026-06-30 23:19 UTCEPSS rescore
  70. 2026-06-30 23:19 UTCEPSS rescore
  71. 2026-06-29 14:03 UTCEPSS rescore
  72. 2026-06-28 14:04 UTCEPSS rescore
  73. 2026-06-28 04:53 UTCEPSS rescore
  74. 2026-06-27 03:05 UTCEPSS rescore
  75. 2026-06-25 13:47 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-9387?
CVE-2016-9387 is a high vulnerability published on March 23, 2017. Integer overflow in the jpcdecprocesssiz function in libjasper/jpc/jpcdec.c in JasPer before 1.900.13 allows remote attackers to have unspecified impact via a crafted file, which triggers an assertion failure.
When was CVE-2016-9387 disclosed?
CVE-2016-9387 was first published on March 23, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-9387 actively exploited?
CVE-2016-9387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-9387?
CVE-2016-9387 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2016-9387?
A fix for CVE-2016-9387 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-9387 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-9387

Explore →

Is Your Infrastructure Affected by CVE-2016-9387?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs