CVE-2019-5427

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 4.9% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

c3p0 version < 0.9.5.4 may be exploited by a billion laughs attack when loading XML configuration due to missing protections against recursive entity expansion when loading configuration.

CVSS v3
7.5
EG Score
7.5HIGHmedium 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
Severity75% × 45%
Exploitation5% × 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
4.9%
EPSS %ILE
91st
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

April 22, 2019

Last Modified

September 5, 2025

References (16)

Vendor Advisories for CVE-2019-5427(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibc3p0-java (0.9.1.2-9+deb8u1ubuntu0.16.04.1~esm1) @ xenial2026-05-27ubuntu
ubuntulibc3p0-java-doc (0.9.1.2-9+deb8u1ubuntu0.14.04.1~esm1) @ trusty2026-05-27ubuntu
ubuntulibc3p0-java (0.9.1.2-10ubuntu0.21.10.1) @ impish2026-05-27ubuntu
redhatc3p02020-03-26redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10, 0.9.1.2-10.1, 0.9.1.2-10.1~deb12u1, 0.9.1.2-11
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
c3p00.9.1.2-10
  • every version up to 0.9.1.2-10.1~deb12u1: fixed in 0.9.1.2-10.1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
c3p0—
  • every version up to 0.9.1.2-10.1: fixed in 0.9.1.2-10.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
c3p0—
  • every version up to 0.9.1.2-10.1: fixed in 0.9.1.2-10.1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.mchange:c3p00.9.2 ... 0.9.5.3 (23 versions)
  • every version up to 0.9.5.4: fixed in 0.9.5.4
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 155 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-5427?
CVE-2019-5427 is a high vulnerability published on April 22, 2019. c3p0 version < 0.9.5.4 may be exploited by a billion laughs attack when loading XML configuration due to missing protections against recursive entity expansion when loading configuration.
When was CVE-2019-5427 disclosed?
CVE-2019-5427 was first published on April 22, 2019, with the most recent update on September 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-5427 actively exploited?
CVE-2019-5427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-5427?
CVE-2019-5427 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-5427?
A fix for CVE-2019-5427 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-5427 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-5427

Explore →

Is Your Infrastructure Affected by CVE-2019-5427?

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

Book a Demo →Browse All CVEs