CVE-2024-45395

LOWNVD 3.13.1
EchelonGraph scoreMEDIUM confidence

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

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2024-09-04. NVD baseline CVSS 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-2773 (ENISA EUVD) · GHSA-cq38-jh5f-37mq (GitHub Security Advisories)Source: ENISA EUVD

3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

sigstore-go, a Go library for Sigstore signing and verification, is susceptible to a denial of service attack in versions prior to 0.6.1 when a verifier is provided a maliciously crafted Sigstore Bundle containing large amounts of verifiable data, in the form of signed transparency log entries, RFC 3161 timestamps, and attestation subjects. The verification of these data structures is computationally expensive. This can be used to consume excessive CPU resources, leading to a denial of service attack. TUF's security model labels this type of vulnerability an "Endless data attack," and can lead to verification failing to complete and disrupting services that rely on sigstore-go for verification. This vulnerability is addressed with sigstore-go 0.6.1, which adds hard limits to the number of verifiable data structures that can be processed in a bundle. Verification will fail if a bundle has data that exceeds these limits. The limits are 32 signed transparency log entries, 32 RFC 3161 timestamps, 1024 attestation subjects, and 32 digests per attestation subject. These limits are intended to be high enough to accommodate the vast majority of use cases, while preventing the verification of maliciously crafted bundles that contain large amounts of verifiable data. Users who are vulnerable but unable to quickly upgrade may consider adding manual bundle validation to enforce limits similar to those in the referenced patch prior to calling sigstore-go's verification functions.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/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)
Severity31% × 45%
Impact severity (EG Severity): CVSS 3.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (3.1): severity, escalated by confirmed exploitation. This CVE's 3.1 is its impact severity (EG Severity), not escalated.

EG Severity
3.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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.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 available. Apply it within your standard update timelines.

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.

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

September 4, 2024

Last Modified

September 24, 2024

References (5)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/sigstore/sigstore-go @ 0.6.1 (fixes <= 0.6.0)—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/sigstore/sigstore-go—
  • every version up to 0.6.1: fixed in 0.6.1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/sigstore/sigstore-go

Frequently asked(5)

What is CVE-2024-45395?
CVE-2024-45395 is a low-severity vulnerability; its CVE record was published on September 4, 2024. sigstore-go, a Go library for Sigstore signing and verification, is susceptible to a denial of service attack in versions prior to 0.6.1 when a verifier is provided a maliciously crafted Sigstore Bundle containing large amounts of verifiable data, in the form of signed transparency log entries, RFC…
When was the CVE record for CVE-2024-45395 published?
The CVE record for CVE-2024-45395 was published on September 4, 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 September 24, 2024; the record at its source may have been updated since.
Is CVE-2024-45395 actively exploited?
CVE-2024-45395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45395?
CVE-2024-45395 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2024-45395?
A fix for CVE-2024-45395 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-45395?

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

Book a Demo →Browse All CVEs