CVE-2023-50868

HIGHNVD 7.58.7
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.7 because EPSS predicted 74% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2023-55601 (ENISA EUVD) · GHSA-pv4h-p8jr-6cv2 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 74%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

CVSS v3
7.5
EG Score
8.7HIGHhigh confidence
EG Risk
78
EG Risk 78/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation74% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
74%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
74% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 14, 2024

Last Modified

December 23, 2025

References (29)

15 of 29 shown · show the other 14

Patch Availability(30)

Vendor / EcosystemFix (by version range) / 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-15.el8_4.22024-06-13redhat
redhatdnsmasq-0:2.79-11.el8_2.32024-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
redhatbind-dyndb-ldap-0:11.9-9.el9_42024-04-30redhat
redhatunbound-0:1.7.3-15.el8_4.12024-04-30redhat
redhatunbound-0:1.13.1-13.el9_0.42024-04-15redhat
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
redhatbind-32:9.11.36-11.el8_9.12024-04-12redhat
redhatbind9.16-32:9.16.23-0.16.el8_9.22024-04-11redhat
redhatbind-dyndb-ldap-0:11.9-8.el9_3.32024-04-11redhat
redhatbind9.16-32:9.16.23-0.14.el8_8.42024-04-02redhat
redhatbind9.16-32:9.16.23-0.7.el8_6.52024-04-02redhat
redhatdnsmasq-0:2.79-21.el8_6.52024-03-27redhat
redhatdnsmasq-0:2.85-3.el9_0.12024-03-27redhat
redhatdnsmasq-0:2.79-26.el8_8.42024-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-5.el8_9.22024-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.

Affected Packages

(50 across 14 ecosystems)
Debian:11(7)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.16.15-1 ... 1:9.16.44-1~deb11u1 (11 versions)
  • every version up to 1:9.16.48-1: fixed in 1:9.16.48-1
—
dnsjava2.1.8-2, 3.6.2-1, 3.6.2-2, 3.6.3-1
  • every version on: no fix on record
—
dnsmasq2.85-1
  • every version up to 2.85-1+deb11u1: fixed in 2.85-1+deb11u1
—
knot-resolver5.3.1-1 ... 6.4.2-1 (43 versions)
  • every version on: no fix on record
—
pdns-recursor4.4.2-3 ... 5.4.5-1 (66 versions)
  • every version on: no fix on record
—
systemd247.3-6 ... 247.3-7+deb11u5 (7 versions)
  • every version up to 247.3-7+deb11u6: fixed in 247.3-7+deb11u6
—
unbound1.13.1-1, 1.13.1-1+deb11u1
  • every version up to 1.13.1-1+deb11u2: fixed in 1.13.1-1+deb11u2
—
Debian:13(7)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.19.21-1: fixed in 1:9.19.21-1
—
dnsjava—
  • every version up to 3.6.2-1: fixed in 3.6.2-1
—
dnsmasq—
  • every version up to 2.90-1: fixed in 2.90-1
—
knot-resolver—
  • every version up to 5.7.1-1: fixed in 5.7.1-1
—
pdns-recursor—
  • every version up to 4.9.3-1: fixed in 4.9.3-1
—
systemd—
  • every version up to 255.4-1: fixed in 255.4-1
—
unbound—
  • every version up to 1.19.1-1: fixed in 1.19.1-1
—
Debian:14(7)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.19.21-1: fixed in 1:9.19.21-1
—
dnsjava—
  • every version up to 3.6.2-1: fixed in 3.6.2-1
—
dnsmasq—
  • every version up to 2.90-1: fixed in 2.90-1
—
knot-resolver—
  • every version up to 5.7.1-1: fixed in 5.7.1-1
—
pdns-recursor—
  • every version up to 4.9.3-1: fixed in 4.9.3-1
—
systemd—
  • every version up to 255.4-1: fixed in 255.4-1
—
unbound—
  • every version up to 1.19.1-1: fixed in 1.19.1-1
—
Debian:12(6)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.18.12-1 ... 1:9.18.24-1~bpo11+1 (8 versions)
  • every version up to 1:9.18.24-1: fixed in 1:9.18.24-1
—
dnsjava2.1.8-2, 3.6.2-1, 3.6.2-2, 3.6.3-1
  • every version on: no fix on record
—
dnsmasq2.89-1, 2.90-1, 2.90-2, 2.90-3
  • every version up to 2.90-4~deb12u1: fixed in 2.90-4~deb12u1
—
knot-resolver5.6.0-1
  • every version up to 5.6.0-1+deb12u1: fixed in 5.6.0-1+deb12u1
—
pdns-recursor4.8.4-1
  • every version up to 4.8.6-1: fixed in 4.8.6-1
—
systemd252.11-1 ... 252.6-1+loong64 (13 versions)
  • every version up to 252.23-1~deb12u1: fixed in 252.23-1~deb12u1
—
Alpine:v3.20(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.21(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.24(3)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
unbound—
  • every version up to 1.19.1-r0: fixed in 1.19.1-r0
—
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.18.24-r0: fixed in 9.18.24-r0
—
dnsmasq—
  • every version up to 2.90-r0: fixed in 2.90-r0
—
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.11.5.P4+dfsg-5.1 ... 1:9.11.5.P4+dfsg-5.1+deb10u9 (11 versions)
  • every version up to 1:9.11.5.P4+dfsg-5.1+deb10u11: fixed in 1:9.11.5.P4+dfsg-5.1+deb10u11
—
unbound1.9.0-2, 1.9.0-2+deb10u1, 1.9.0-2+deb10u2, 1.9.0-2+deb10u3
  • every version up to 1.9.0-2+deb10u4: fixed in 1.9.0-2+deb10u4
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.0.0 up to 9.16.48-r0: fixed in 9.16.48-r0
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 9× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 87 of 135 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 13 repeat rows among the latest 100 are merged into the row they repeat. The 48 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:31 UTCEPSS rescoreEPSS 74% · 99th percentile
  2. 2026-10-27 19:35 UTCEG score recompute
  3. 2026-10-27 19:35 UTCVendor advisory
  4. 2026-10-27 19:35 UTCGHSA enrichmentGHSA-pv4h-p8jr-6cv2 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-27 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  6. 2026-10-26 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  7. 2026-10-25 17:30 UTCEG score recompute
  8. 2026-10-25 16:30 UTCEPSS rescoreEPSS 74% · 99th percentile
  9. 2026-10-24 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  10. 2026-10-22 16:31 UTCEPSS rescoreEPSS 74% · 99th percentile
  11. 2026-10-21 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  12. 2026-10-20 21:33 UTCEG score recompute
  13. 2026-10-20 21:33 UTCVendor advisory
  14. 2026-10-20 21:33 UTCGHSA enrichmentGHSA-pv4h-p8jr-6cv2 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-20 16:30 UTCEPSS rescoreEPSS 74% · 99th percentile
  16. 2026-10-19 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  17. 2026-10-18 07:44 UTCEG score recompute
  18. 2026-10-15 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  19. 2026-10-14 16:30 UTCEPSS rescoreEPSS 74% · 99th percentile
  20. 2026-10-13 16:30 UTCEPSS rescoreEPSS 74% · 99th percentile
  21. 2026-10-12 18:14 UTCEG score recompute
  22. 2026-10-11 23:54 UTCOSV refresh
  23. 2026-10-11 21:40 UTCEG score recompute
  24. 2026-10-10 19:57 UTCEPSS rescoreEPSS 74% · 99th percentile
  25. 2026-10-09 20:05 UTCEPSS rescoreEPSS 74% · 99th percentile
Show 62 more
  1. 2026-10-07 23:46 UTCEPSS rescoreEPSS 74% · 99th percentile
  2. 2026-10-06 15:15 UTCEPSS rescoreEPSS 74% · 99th percentile
  3. 2026-10-01 19:48 UTCEPSS rescoreEPSS 74% · 99th percentile
  4. 2026-09-30 16:35 UTCEG score recompute▼ 0.20
  5. 2026-09-29 15:17 UTCEPSS rescoreEPSS 74% · 99th percentile
  6. 2026-09-28 13:49 UTCEPSS rescoreEPSS 82% · 99th percentile
  7. 2026-09-26 00:22 UTCEPSS rescoreEPSS 82% · 99th percentile
  8. 2026-09-24 14:01 UTCEPSS rescoreEPSS 82% · 99th percentile
  9. 2026-09-23 13:46 UTCEPSS rescoreEPSS 82% · 99th percentile
  10. 2026-09-22 14:46 UTCEPSS rescoreEPSS 82% · 99th percentile
  11. 2026-09-22 07:46 UTCOSV refresh
  12. 2026-09-21 20:31 UTCEPSS rescoreEPSS 82% · 99th percentile
  13. 2026-09-20 20:14 UTCEPSS rescoreEPSS 82% · 99th percentile
  14. 2026-09-18 19:26 UTCEPSS rescoreEPSS 82% · 99th percentile
  15. 2026-09-16 14:06 UTCEPSS rescoreEPSS 82% · 99th percentile
  16. 2026-09-16 05:11 UTCEPSS rescoreEPSS 82% · 99th percentile
  17. 2026-09-12 14:58 UTCEPSS rescoreEPSS 82% · 99th percentile
  18. 2026-09-06 13:45 UTCEPSS rescoreEPSS 82% · 99th percentile
  19. 2026-09-05 15:26 UTCEPSS rescoreEPSS 82% · 99th percentile
  20. 2026-09-04 13:58 UTCEPSS rescoreEPSS 82% · 99th percentile
  21. 2026-09-03 05:00 UTCOSV refresh
  22. 2026-09-01 13:51 UTCEPSS rescoreEPSS 82% · 99th percentile
  23. 2026-09-01 04:35 UTCEPSS rescoreEPSS 82% · 99th percentile
  24. 2026-08-30 19:15 UTCEPSS rescoreEPSS 82% · 99th percentile
  25. 2026-08-30 01:20 UTCEPSS rescoreEPSS 82% · 99th percentile
  26. 2026-08-28 21:39 UTCEPSS rescoreEPSS 82% · 99th percentile
  27. 2026-08-26 14:44 UTCEPSS rescoreEPSS 82% · 99th percentile
  28. 2026-08-24 14:14 UTCEPSS rescoreEPSS 82% · 99th percentile
  29. 2026-08-21 23:47 UTCEPSS rescoreEPSS 82% · 99th percentile
  30. 2026-08-19 17:02 UTCEPSS rescoreEPSS 82% · 99th percentile
  31. 2026-08-18 13:46 UTCEPSS rescoreEPSS 82% · 99th percentile
  32. 2026-08-16 18:26 UTCOSV refresh
  33. 2026-08-16 02:12 UTCEPSS rescoreEPSS 82% · 99th percentile
  34. 2026-08-15 01:28 UTCEPSS rescoreEPSS 82% · 99th percentile
  35. 2026-08-12 13:49 UTCEPSS rescoreEPSS 82% · 99th percentile
  36. 2026-08-10 23:57 UTCEPSS rescoreEPSS 82% · 99th percentile
  37. 2026-08-05 19:15 UTCEPSS rescoreEPSS 82% · 99th percentile
  38. 2026-08-01 12:36 UTCOSV refresh
  39. 2026-07-30 16:26 UTCEPSS rescoreEPSS 82% · 99th percentile
  40. 2026-07-30 01:28 UTCEPSS rescoreEPSS 82% · 99th percentile
  41. 2026-07-28 15:34 UTCEPSS rescoreEPSS 82% · 99th percentile
  42. 2026-07-26 14:52 UTCEPSS rescoreEPSS 82% · 99th percentile
  43. 2026-07-25 14:16 UTCEPSS rescoreEPSS 82% · 99th percentile
  44. 2026-07-24 14:16 UTCEPSS rescoreEPSS 82% · 99th percentile
  45. 2026-07-23 02:28 UTCEG score recompute▲ 1.40
  46. 2026-07-22 23:15 UTCEG score recompute
  47. 2026-07-22 14:06 UTCEPSS rescoreEPSS 82% · 99th percentile
  48. 2026-07-20 17:06 UTCEPSS rescoreEPSS 82% · 99th percentile
  49. 2026-07-19 14:29 UTCEPSS rescoreEPSS 82% · 99th percentile
  50. 2026-07-19 02:27 UTCEPSS rescoreEPSS 82% · 99th percentile
  51. 2026-07-15 16:56 UTCEPSS rescoreEPSS 82% · 99th percentile
  52. 2026-07-15 01:59 UTCEPSS rescoreEPSS 82% · 99th percentile
  53. 2026-07-14 19:40 UTCOSV refresh
  54. 2026-07-11 08:26 UTCEPSS rescoreEPSS 82% · 99th percentile
  55. 2026-07-07 13:44 UTCEPSS rescoreEPSS 82% · 99th percentile
  56. 2026-07-02 16:59 UTCEPSS rescoreEPSS 82% · 99th percentile
  57. 2026-07-01 15:05 UTCEPSS rescoreEPSS 82% · 99th percentile
  58. 2026-06-28 04:55 UTCEPSS rescoreEPSS 82% · 99th percentile
  59. 2026-06-27 03:07 UTCEPSS rescoreEPSS 82% · 99th percentile
  60. 2026-06-26 20:37 UTCOSV refresh
  61. 2026-06-25 13:48 UTCEPSS rescoreEPSS 82% · 99th percentile
  62. 2026-06-23 21:31 UTCEPSS rescoreEPSS 82% · 99th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCGoethe-Universitat-Cybersecurity/NSEC3-Encloser-Attack
    Published Mar 19, 2024

    This project generates DNS zonefiles with custom NSEC3 parameters to reproduce and evaluate the attacks in CVE-2023-50868.

    Open source ↗

Frequently asked(5)

What is CVE-2023-50868?
CVE-2023-50868 is a high-severity vulnerability; its CVE record was published on February 14, 2024. The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification…
When was the CVE record for CVE-2023-50868 published?
The CVE record for CVE-2023-50868 was published on February 14, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of December 23, 2025; the record at its source may have been updated since.
Is CVE-2023-50868 actively exploited?
CVE-2023-50868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-50868?
CVE-2023-50868 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.7 (HIGH).
How do I remediate CVE-2023-50868?
A fix for CVE-2023-50868 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-50868 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-2023-50868

Explore →

Is Your Infrastructure Affected by CVE-2023-50868?

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