CVE-2023-3724

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: HIGH) published 2023-07-18. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-44359 (ENISA EUVD) · GHSA-h4rv-393v-2f5h (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

If a TLS 1.3 client gets neither a PSK (pre shared key) extension nor a KSE (key share extension) when connecting to a malicious server, a default predictable buffer gets used for the IKM (Input Keying Material) value when generating the session master secret. Using a potentially known IKM value when generating the session master secret key compromises the key generated, allowing an eavesdropper to reconstruct it and potentially allowing access to or meddling with message contents in the session. This issue does not affect client validation of connected servers, nor expose private key information, but could result in an insecure TLS 1.3 session when not controlling both sides of the connection. wolfSSL recommends that TLS 1.3 client side users update the version of wolfSSL used. 

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.7%
EPSS %ILE
51st
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 17, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 2, 2026
Patch available. Sources: github_pr.
Web pageMentions a patch (unverified)

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
GitHub pull request

add tls extension sanity check

Fix merged in wolfSSL/wolfssl PR #6412 on 2023-05-17 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/6412

Vendor Advisories for CVE-2023-3724(1)

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

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.6.2-r0: fixed in 5.6.2-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl4.6.0+p1-0+deb11u1, 4.6.0-3
  • every version up to 4.6.0+p1-0+deb11u2: fixed in 4.6.0+p1-0+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl5.5.4-2
  • every version up to 5.5.4-2+deb12u1: fixed in 5.5.4-2+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wolfssl—
  • every version up to 5.5.4-2.1: fixed in 5.5.4-2.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 83× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 326 rows 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. None are among the latest 100 rows. The 226 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 15:05 UTCEchelonGraph re-scored
  2. 2026-11-13 15:05 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  3. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-11-12 16:23 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  5. 2026-11-11 17:37 UTCEchelonGraph re-scored
  6. 2026-11-11 17:37 UTCVendor advisory
  7. 2026-11-11 17:37 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  8. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-11-10 18:55 UTCEchelonGraph re-scored
  10. 2026-11-10 18:55 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  11. 2026-11-10 16:37 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-11-09 20:13 UTCEchelonGraph re-scored
  13. 2026-11-09 20:13 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  14. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-11-08 21:31 UTCEchelonGraph re-scored
  16. 2026-11-08 21:31 UTCVendor advisory
  17. 2026-11-08 21:31 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  18. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-11-07 22:49 UTCEchelonGraph re-scored
  20. 2026-11-07 22:49 UTCVendor advisory
  21. 2026-11-07 22:49 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  22. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-11-07 00:06 UTCEchelonGraph re-scored
  24. 2026-11-07 00:06 UTCVendor advisory
  25. 2026-11-07 00:06 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
Show 75 more
  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-11-06 01:22 UTCEchelonGraph re-scored
  3. 2026-11-06 01:22 UTCVendor advisory
  4. 2026-11-06 01:22 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  5. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-11-05 02:41 UTCEchelonGraph re-scored
  7. 2026-11-05 02:41 UTCVendor advisory
  8. 2026-11-05 02:41 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  9. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-11-04 14:25 UTCOSV refresh
  11. 2026-11-04 03:59 UTCEchelonGraph re-scored
  12. 2026-11-04 03:59 UTCVendor advisory
  13. 2026-11-04 03:59 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  14. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-11-03 05:17 UTCEchelonGraph re-scored
  16. 2026-11-03 05:17 UTCVendor advisory
  17. 2026-11-03 05:17 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  18. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-11-02 06:34 UTCEchelonGraph re-scored
  20. 2026-11-02 06:34 UTCVendor advisory
  21. 2026-11-02 06:34 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  22. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-11-01 07:53 UTCEchelonGraph re-scored
  24. 2026-11-01 07:53 UTCVendor advisory
  25. 2026-11-01 07:53 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  26. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-31 09:10 UTCEchelonGraph re-scored
  28. 2026-10-31 09:10 UTCVendor advisory
  29. 2026-10-31 09:10 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  30. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-30 10:28 UTCEchelonGraph re-scored
  32. 2026-10-30 10:28 UTCVendor advisory
  33. 2026-10-30 10:28 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  34. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-29 11:47 UTCEchelonGraph re-scored
  36. 2026-10-29 11:47 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  37. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-10-28 13:05 UTCEchelonGraph re-scored
  39. 2026-10-28 13:05 UTCVendor advisory
  40. 2026-10-28 13:04 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  41. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-10-27 14:21 UTCEchelonGraph re-scored
  43. 2026-10-27 14:21 UTCVendor advisory
  44. 2026-10-27 14:21 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  45. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-10-26 15:19 UTCEchelonGraph re-scored
  47. 2026-10-26 15:19 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  48. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-10-25 15:44 UTCEchelonGraph re-scored
  50. 2026-10-25 15:44 UTCVendor advisory
  51. 2026-10-25 15:43 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  52. 2026-10-24 16:57 UTCEchelonGraph re-scored
  53. 2026-10-24 16:57 UTCVendor advisory
  54. 2026-10-24 16:57 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  55. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-10-23 18:16 UTCEchelonGraph re-scored
  57. 2026-10-23 18:16 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  58. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-10-22 19:15 UTCEchelonGraph re-scored
  60. 2026-10-22 19:15 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  61. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-10-21 20:34 UTCEchelonGraph re-scored
  63. 2026-10-21 20:34 UTCVendor advisory
  64. 2026-10-21 20:34 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  65. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-10-20 21:51 UTCEchelonGraph re-scored
  67. 2026-10-20 21:51 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  68. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-10-19 23:10 UTCEchelonGraph re-scored
  70. 2026-10-19 23:10 UTCVendor advisory
  71. 2026-10-19 23:09 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1
  72. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-10-18 22:34 UTCEchelonGraph re-scored
  74. 2026-10-18 22:34 UTCVendor advisory
  75. 2026-10-18 22:34 UTCGHSA enrichmentGHSA-h4rv-393v-2f5h · GitHub severity HIGH · GitHub CVSS 9.1

Frequently asked(5)

What is CVE-2023-3724?
CVE-2023-3724 is a critical-severity vulnerability; its CVE record was published on July 17, 2023. If a TLS 1.3 client gets neither a PSK (pre shared key) extension nor a KSE (key share extension) when connecting to a malicious server, a default predictable buffer gets used for the IKM (Input Keying Material) value when generating the session master secret. Using a potentially known IKM value…
When was CVE-2023-3724 made public?
CVE-2023-3724 was made public on June 9, 2023: that is the date its CVE record's CNA, wolfSSL Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 17, 2023. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-3724 actively exploited?
CVE-2023-3724 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-3724?
CVE-2023-3724 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-3724?
A fix for CVE-2023-3724 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-3724 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-3724

Explore →

Is Your Infrastructure Affected by CVE-2023-3724?

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