CVE-2017-5645

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 89.0%, top 0% of all CVEs by exploit prediction. 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
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
84(Track*)
EG Risk 84/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
Severity98% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
90%
EPSS %ILE
100%
KEV
Not listed

Published

April 17, 2017

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Sep 14, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2017:1801
redhat Patch Available
https://access.redhat.com/errata/RHSA-2017:1417
generic

CVE-2017-5645 - PSIRT.COM

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

oss-security - [CVE-2019-17571] Apache Log4j 1.2 deserialization of untrusted data in SocketServer

http://www.openwall.com/lists/oss-security/2019/12/19/2
generic
http://www.securitytracker.com/id/1041294
generic
http://www.securitytracker.com/id/1040200

Vendor Advisories for CVE-2017-5645(16)

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathawtio-osgi2021-08-11redhat
redhatlog4j2019-06-18redhat
redhatpatch2017-12-07redhat
redhatlog4j-0:1.2.14-19.patch_01.ep5.el62017-12-07redhat
redhatpatch2017-11-16redhat
redhatpatch2017-09-26redhat
redhateap7-wildfly-javadocs-0:7.0.8-1.GA_redhat_1.1.ep7.el62017-09-26redhat
redhateap7-wildfly-javadocs-0:7.0.8-1.GA_redhat_1.1.ep7.el72017-09-26redhat
redhateap7-jboss-ec2-eap-0:7.0.8-1.GA_redhat_1.ep7.el72017-09-26redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el62017-09-05redhat
redhatjboss-ec2-eap-0:7.5.17-1.Final_redhat_4.ep6.el62017-09-05redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el72017-09-05redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el52017-09-05redhat
redhatpatch2017-09-05redhat
redhatlog4j-0:1.2.17-16.el7_42017-08-07redhat
redhattomcat-native-0:1.2.8-10.redhat_10.ep7.el72017-07-25redhat
redhatrh-java-common-log4j-0:1.2.17-15.15.el72017-06-08redhat

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 5 ecosystems)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.logging.log4j:log4j2.0 ... 2.8.1 (17 versions)2.8.2—
org.apache.logging.log4j:log4j-core2.0 ... 2.8.1 (17 versions)2.8.2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache-log4j2—2.7-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache-log4j2—2.7-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache-log4j2—2.7-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache-log4j2—2.7-2—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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 3× in last 7d / 9× 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.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-15 06:55 UTCOSV refresh
  3. 2026-09-12 14:55 UTCEPSS rescore
  4. 2026-09-06 13:43 UTCEPSS rescore
  5. 2026-09-05 15:23 UTCEPSS rescore
  6. 2026-09-04 13:56 UTCEPSS rescore
  7. 2026-08-30 19:13 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-27 06:34 UTCOSV refresh
  10. 2026-08-19 16:59 UTCEPSS rescore
  11. 2026-08-18 13:43 UTCEPSS rescore
  12. 2026-08-17 13:42 UTCEPSS rescore
  13. 2026-08-16 14:51 UTCEPSS rescore
  14. 2026-08-15 01:26 UTCEPSS rescore
  15. 2026-08-12 13:46 UTCEPSS rescore
  16. 2026-08-10 20:08 UTCOSV refresh
  17. 2026-07-30 16:24 UTCEPSS rescore
  18. 2026-07-28 15:32 UTCEPSS rescore
  19. 2026-07-25 20:01 UTCOSV refresh
  20. 2026-07-23 01:29 UTCEG score recompute
  21. 2026-07-22 22:09 UTCEG score recompute
  22. 2026-07-22 14:04 UTCEPSS rescore
  23. 2026-07-22 14:04 UTCEPSS rescore
  24. 2026-07-21 15:21 UTCEPSS rescore
  25. 2026-07-21 15:21 UTCEPSS rescore
Show 31 more
  1. 2026-07-15 16:54 UTCEPSS rescore
  2. 2026-07-08 14:45 UTCOSV refresh
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-20 02:42 UTCOSV refresh
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-10 13:19 UTCEPSS rescore
  14. 2026-06-06 13:45 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-05-31 03:55 UTCOSV refresh
  17. 2026-05-29 13:41 UTCEPSS rescore
  18. 2026-05-26 07:17 UTCEPSS rescore
  19. 2026-05-26 07:17 UTCEPSS rescore
  20. 2026-05-20 11:02 UTCVendor advisory
  21. 2026-05-20 07:11 UTCVendor advisory
  22. 2026-05-20 03:19 UTCVendor advisory
  23. 2026-05-19 23:28 UTCVendor advisory
  24. 2026-05-19 19:37 UTCVendor advisory
  25. 2026-05-19 15:45 UTCVendor advisory
  26. 2026-05-19 11:53 UTCVendor advisory
  27. 2026-05-19 07:58 UTCVendor advisory
  28. 2026-05-19 04:06 UTCVendor advisory
  29. 2026-05-19 00:13 UTCEG score recompute
  30. 2026-05-19 00:13 UTCVendor advisory
  31. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 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 PoCHynekPetrak/log4shell-finder
    First seen Dec 14, 2021

    Fastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other vulnerable (CVE-2017-5645, CVE-2019-17571, CVE-2022-23305, CVE-2022-23307 ... ) instances of log4j library. Excellent performance and low memory footprint.

    Open source ↗
  • GitHub PoCpimps/CVE-2017-5645
    First seen Aug 4, 2017

    CVE-2017-5645 - Apache Log4j RCE due Insecure Deserialization

    Open source ↗
  • Nucleinetwork/cves/2017/CVE-2017-5645.yaml
    First seen Jan 1, 2017

    Apache Log4j Server - Deserialization Command Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-5645?
CVE-2017-5645 is a critical vulnerability published on April 17, 2017. In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.
When was CVE-2017-5645 disclosed?
CVE-2017-5645 was first published in the National Vulnerability Database on April 17, 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-2017-5645 actively exploited?
CVE-2017-5645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2017-5645?
CVE-2017-5645 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-5645?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5645, 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-2017-5645

Explore →

Is Your Infrastructure Affected by CVE-2017-5645?

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

Start Free Scan →Browse All CVEs