CVE-2024-23332

MEDIUMNVD 4.04.0
EchelonGraph scoreMEDIUM confidence

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

Score 4.0 from GitHub Security Advisory published 2024-01-19. NVD baseline CVSS 4.0; sources differ by 0.0.

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

Also known asEUVD-2024-0257 (ENISA EUVD) · GHSA-57wx-m636-g3g8 (GitHub Security Advisories)Source: ENISA EUVD

4.0EG
EchelonGraph verdictMonitorNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.0Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images. This could lead artifact consumers with relaxed trust policies (such as permissive instead of strict) to potentially use artifacts with signatures that are no longer valid, making them susceptible to any exploits those artifacts may contain. In Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process. Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts. Artifact consumers should correspondingly use a strict or equivalent trust policy that enforces signature expiry. Together these steps enable use of up-to-date artifacts and safeguard against rollback attack in the event of registry compromise. The Notary Project offers various signature validation options such as permissive, audit and skip to support various scenarios. These scenarios includes 1) situations demanding urgent workload deployment, necessitating the bypassing of expired or revoked signatures; 2) auditing of artifacts lacking signatures without interrupting workload; and 3) skipping of verification for specific images that might have undergone validation through alternative mechanisms. Additionally, the Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary. This revocation serves as a signal to inform artifact consumers that the corresponding unexpired artifact is no longer approved by the publisher. This enables the artifact publisher to control the validity of the signature independently of their ability to manage artifacts in a compromised registry.

CVSS v3
4.0
EG Score
4.0MEDIUMmedium confidence
EG Risk
18
EG Risk 18/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)
Severity40% × 45%
Impact severity (EG Severity): CVSS 4.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (4.0): severity, escalated by confirmed exploitation. This CVE's 4.0 is its impact severity (EG Severity), not escalated.

EG Severity
4.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

January 19, 2024

Last Modified

November 21, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/notaryproject/notation—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/notaryproject/notation—
  • every version through 1.0.0: no fix on record
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 97 of 208 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/notaryproject/notation

Frequently asked(5)

What is CVE-2024-23332?
CVE-2024-23332 is a medium-severity vulnerability; its CVE record was published on January 19, 2024. The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compromised container registry can provide outdated versions of…
When was the CVE record for CVE-2024-23332 published?
The CVE record for CVE-2024-23332 was published on January 19, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2024-23332 actively exploited?
CVE-2024-23332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-23332?
CVE-2024-23332 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2024-23332?
A fix for CVE-2024-23332 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-23332

Explore →

Is Your Infrastructure Affected by CVE-2024-23332?

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

Book a Demo →Browse All CVEs