CVE-2024-49113

HIGHNVD 7.58.9
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 83% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 83%CVSS: 7.5Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Windows Lightweight Directory Access Protocol (LDAP) Denial of Service Vulnerability

CVSS v3
7.5
EG Score
8.9(high)
EG Risk
88(Attend)
EG Risk 88/100SSVC: Attend

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
Severity89% × 45%
Exploitation83% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
83%
EPSS %ILE
100%
KEV
Not listed

Published

December 12, 2024

Last Modified

January 14, 2025

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 19× 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-08-06 13:45 UTCEPSS rescore
  2. 2026-07-28 15:35 UTCEPSS rescore
  3. 2026-07-26 14:53 UTCEPSS rescore
  4. 2026-07-26 14:53 UTCEPSS rescore
  5. 2026-07-24 14:16 UTCEPSS rescore
  6. 2026-07-23 02:42 UTCEG score recompute 0.10
  7. 2026-07-22 14:07 UTCEPSS rescore
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-21 15:23 UTCEPSS rescore
  10. 2026-07-20 17:06 UTCEPSS rescore
  11. 2026-07-19 14:30 UTCEPSS rescore
  12. 2026-07-19 14:30 UTCEPSS rescore
  13. 2026-07-19 02:28 UTCEPSS rescore
  14. 2026-07-19 02:28 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-01 15:05 UTCEPSS rescore
  22. 2026-06-28 04:55 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 21 more
  1. 2026-06-23 21:32 UTCEPSS rescore
  2. 2026-06-16 17:52 UTCEPSS rescore
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 17:47 UTCEPSS rescore
  5. 2026-06-14 23:17 UTCEPSS rescore
  6. 2026-06-13 22:59 UTCEPSS rescore
  7. 2026-06-13 22:59 UTCEPSS rescore
  8. 2026-06-13 22:59 UTCEPSS rescore
  9. 2026-06-10 22:18 UTCEPSS rescore
  10. 2026-06-10 13:21 UTCEPSS rescore
  11. 2026-06-05 22:46 UTCEPSS rescore
  12. 2026-06-05 22:46 UTCEPSS rescore
  13. 2026-06-02 20:12 UTCEPSS rescore
  14. 2026-06-01 13:51 UTCEPSS rescore
  15. 2026-06-01 13:51 UTCEPSS rescore
  16. 2026-05-28 13:44 UTCEPSS rescore
  17. 2026-05-28 13:44 UTCEPSS rescore
  18. 2026-05-28 13:44 UTCEPSS rescore
  19. 2026-05-23 16:32 UTCEG score recompute
  20. 2026-05-23 16:32 UTCVendor advisory
  21. 2026-05-23 16:32 UTCGHSA enrichment

Publicly available exploits

(1 reference)

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

  • GitHub PoCSachinart/CVE-2024-49113-Checker
    First seen Jan 6, 2025

    Hi, This is to check targets vulnerable for CVE-2024-49113 in bulk, faster.

    Open source ↗

Frequently asked(5)

What is CVE-2024-49113?
CVE-2024-49113 is a high vulnerability published on December 12, 2024. Windows Lightweight Directory Access Protocol (LDAP) Denial of Service Vulnerability
When was CVE-2024-49113 disclosed?
CVE-2024-49113 was first published in the National Vulnerability Database on December 12, 2024, with the most recent update on January 14, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-49113 actively exploited?
CVE-2024-49113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2024-49113?
CVE-2024-49113 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2024-49113?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-49113, 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

Explore the affected products and dependency analysis for CVE-2024-49113

Explore →

Is Your Infrastructure Affected by CVE-2024-49113?

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