CVE-2023-50387

HIGHNVD 7.59.0
EchelonGraph scoreMEDIUM confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 100%
CISA-KEV: Not listedEPSS: 100%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

CVSS v3
7.5
EG Score
9.0(medium)
EG Risk
95(Track)
EG Risk 95/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
Severity90% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
100.0%
KEV
Not listed

Published

February 14, 2024

Last Modified

November 4, 2025

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbind-dyndb-ldap-0:2.3-8.el6_10.12025-01-06redhat
redhatunbound-0:1.6.6-5.el7_9.12024-12-12redhat
redhatdnsmasq-0:2.79-11.el8_2.32024-06-13redhat
redhatdnsmasq-0:2.79-15.el8_4.22024-06-13redhat
redhatdhcp-12:4.2.5-83.el7_9.22024-06-10redhat
redhatbind-32:9.11.36-14.el8_102024-05-22redhat
redhatdhcp-12:4.3.6-40.el8_2.32024-05-16redhat
redhatdhcp-12:4.3.6-44.el8_4.32024-05-13redhat
redhatdhcp-12:4.3.6-49.el8_8.12024-05-07redhat
redhatdhcp-12:4.3.6-47.el8_6.22024-05-07redhat
redhatunbound-0:1.7.3-12.el8_2.12024-05-06redhat
redhatunbound-0:1.7.3-15.el8_4.12024-04-30redhat
redhatbind-dyndb-ldap-0:11.9-9.el9_42024-04-30redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_2.22024-04-15redhat
redhatbind-dyndb-ldap-0:11.9-7.el9_0.12024-04-15redhat
redhatunbound-0:1.7.3-17.el8_6.42024-04-15redhat
redhatunbound-0:1.13.1-13.el9_0.42024-04-15redhat
redhatbind-32:9.11.36-11.el8_9.12024-04-12redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_3.32024-04-11redhat
redhatbind9.16-32:9.16.23-0.16.el8_9.22024-04-11redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.52024-04-02redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.42024-04-02redhat
redhatdnsmasq-0:2.79-26.el8_8.42024-03-27redhat
redhatdnsmasq-0:2.85-3.el9_0.12024-03-27redhat
redhatdnsmasq-0:2.79-21.el8_6.52024-03-27redhat
redhatdnsmasq-0:2.85-6.el9_2.32024-03-26redhat
redhatdnsmasq-0:2.79-31.el8_9.22024-03-14redhat
redhatdnsmasq-0:2.85-14.el9_3.12024-03-14redhat
redhatunbound-0:1.16.2-5.el8_8.12024-02-27redhat
redhatunbound-0:1.16.2-3.el9_3.12024-02-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.

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 4× in last 7d / 7× 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-07-23 02:28 UTCEG score recompute
  2. 2026-07-22 21:23 UTCEG score recompute 1.50
  3. 2026-07-22 21:23 UTCVendor advisory
  4. 2026-07-22 21:22 UTCGHSA enrichment
  5. 2026-07-14 19:40 UTCOSV refresh
  6. 2026-07-08 15:13 UTCEPSS rescore
  7. 2026-06-26 20:37 UTCOSV refresh
  8. 2026-06-15 17:47 UTCEPSS rescore
  9. 2026-06-12 23:11 UTCEPSS rescore
  10. 2026-06-12 23:10 UTCEPSS rescore
  11. 2026-06-11 13:59 UTCEPSS rescore
  12. 2026-06-10 22:17 UTCEPSS rescore
  13. 2026-06-10 13:21 UTCEPSS rescore
  14. 2026-06-09 06:30 UTCOSV refresh
  15. 2026-06-08 14:16 UTCEPSS rescore
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-07 15:23 UTCEPSS rescore
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-05 06:09 UTCEPSS rescore
Show 21 more
  1. 2026-06-04 13:11 UTCEPSS rescore
  2. 2026-06-04 13:11 UTCEPSS rescore
  3. 2026-06-04 13:11 UTCEPSS rescore
  4. 2026-06-02 20:12 UTCEPSS rescore
  5. 2026-06-02 20:12 UTCEPSS rescore
  6. 2026-05-31 22:30 UTCEPSS rescore
  7. 2026-05-31 22:30 UTCEPSS rescore
  8. 2026-05-31 00:15 UTCEPSS rescore
  9. 2026-05-31 00:15 UTCEPSS rescore
  10. 2026-05-29 13:43 UTCEPSS rescore
  11. 2026-05-28 13:44 UTCEPSS rescore
  12. 2026-05-27 13:39 UTCEPSS rescore
  13. 2026-05-27 13:39 UTCEPSS rescore
  14. 2026-05-26 13:43 UTCEPSS rescore
  15. 2026-05-26 13:43 UTCEPSS rescore
  16. 2026-05-26 07:18 UTCEPSS rescore
  17. 2026-05-26 07:18 UTCEPSS rescore
  18. 2026-05-26 07:18 UTCEPSS rescore
  19. 2026-05-24 08:31 UTCEG score recompute
  20. 2026-05-24 08:31 UTCVendor advisory
  21. 2026-05-24 08:31 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 PoCknqyf263/CVE-2023-50387
    First seen Feb 18, 2024

    KeyTrap (DNSSEC)

    Open source ↗

Frequently asked(5)

What is CVE-2023-50387?
CVE-2023-50387 is a high vulnerability published on February 14, 2024. Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG…
When was CVE-2023-50387 disclosed?
CVE-2023-50387 was first published in the National Vulnerability Database on February 14, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-50387 actively exploited?
CVE-2023-50387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 100.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-50387?
CVE-2023-50387 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2023-50387?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-50387, 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-2023-50387

Explore →

Is Your Infrastructure Affected by CVE-2023-50387?

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