CVE-2019-12384

MEDIUMNVD 5.96.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 6.8 because EPSS predicts 45% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 45%CVSS: 5.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.

CVSS v3
5.9
EG Score
6.8(high)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

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
Severity68% × 45%
Exploitation45% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
45%
EPSS %ILE
99%
KEV
Not listed

Published

June 24, 2019

Last Modified

November 21, 2024

References (92)

Vendor Advisories for CVE-2019-12384(16)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibjackson2-databind-java-doc (2.4.2-3ubuntu0.1~esm2) @ xenial2026-05-27ubuntu
redhateap7-jackson-databind-0:2.8.11.5-1.redhat_00001.1.ep7.el72024-08-26redhat
redhatjackson-databind2020-03-26redhat
redhatpatch2019-10-24redhat
redhatopenshift3/ose-logging-elasticsearch5:v3.11.153-22019-10-18redhat
redhatpatch2019-10-10redhat
redhateap7-wildfly-transaction-client-0:1.1.6-2.Final_redhat_00001.1.el7eap2019-10-01redhat
redhateap7-wildfly-transaction-client-0:1.1.6-2.Final_redhat_00001.1.el6eap2019-10-01redhat
redhateap7-wildfly-transaction-client-0:1.1.6-2.Final_redhat_00001.1.el8eap2019-10-01redhat
redhatopenshift4/ose-logging-elasticsearch5:v4.1.18-2019092019152019-09-27redhat
redhatpki-deps:10.6-8000020190807021343.f8e95b4e2019-09-12redhat
redhatrh-maven35-jackson-databind-0:2.7.6-2.6.el72019-07-22redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jackson-databind—2.9.8-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jackson-databind—2.9.8-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jackson-databind—2.9.8-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jackson-databind—2.9.8-3—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.4.2-2 ... 2.4.2-2+deb8u6 (7 versions)2.4.2-2+deb8u7—
Maven(1)
PackageVulnerable rangeFixed inDependents
com.fasterxml.jackson.core:jackson-databind2.0.0 ... 2.6.7.2 (61 versions)2.6.7.3—

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 / 23× 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 109 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCMagicZer0/Jackson_RCE-CVE-2019-12384
    First seen Jul 26, 2019

    CVE-2019-12384 漏洞测试环境

    Open source ↗
  • GitHub PoCjas502n/CVE-2019-12384
    First seen Jul 24, 2019

    Jackson Rce For CVE-2019-12384

    Open source ↗

Frequently asked(5)

What is CVE-2019-12384?
CVE-2019-12384 is a medium vulnerability published on June 24, 2019. FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.
When was CVE-2019-12384 disclosed?
CVE-2019-12384 was first published in the National Vulnerability Database on June 24, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-12384 actively exploited?
CVE-2019-12384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
What is the CVSS score of CVE-2019-12384?
CVE-2019-12384 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.8.
How do I remediate CVE-2019-12384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-12384, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-12384?

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

Start Free Scan →Browse All CVEs