CVE-2024-57823

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2025-01-10. NVD baseline CVSS 9.3; sources differ by 0.0.

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

Also known asEUVD-2024-53767 (ENISA EUVD) · GHSA-4mjp-wj5r-mc96 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In Raptor RDF Syntax Library through 2.0.16, there is an integer underflow when normalizing a URI with the turtle parser in raptor_uri_normalize_path().

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
28th
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-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-11-02). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

January 10, 2025

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4343-1] raptor2 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00023.html
Web page

PoC/fuzzing/raptor-fuzz.md at master · pedrib/PoC · GitHub

https://github.com/pedrib/PoC/blob/master/fuzzing/raptor-fuzz.md
Web page

Heap read overflow and integer overflow in memcpy · Issue #70 · dajobe/raptor · GitHub

https://github.com/dajobe/raptor/issues/70
Web pageMentions a patch (unverified)

#1067896 - raptor2: CVE-2024-57822 CVE-2024-57823: memcpy integer underflow and heap read overflow - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067896

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturaptor2-utils (2.0.14-1ubuntu0.16.04.1+esm1) @ xenial2026-11-03ubuntu
ubunturaptor2-utils (2.0.16-4ubuntu0.1) @ oracular2026-11-03ubuntu
redhatraptor2-0:2.0.15-17.el8_62025-01-15redhat
redhatraptor2-0:2.0.15-17.el8_42025-01-14redhat
redhatraptor2-0:2.0.9-5.el7_92025-01-14redhat
redhatraptor2-0:2.0.15-17.el8_102025-01-14redhat
redhatraptor2-0:2.0.15-17.el8_82025-01-14redhat
redhatraptor2-0:2.0.15-17.el8_22025-01-14redhat
redhatraptor2-0:2.0.15-31.el9_02025-01-14redhat
redhatraptor2-0:2.0.15-31.el9_22025-01-14redhat
redhatraptor2-0:2.0.15-31.el9_42025-01-14redhat
redhatraptor2-0:2.0.15-32.el9_52025-01-14redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
raptor22.0.14-1.2
  • every version up to 2.0.14-1.2+deb11u1: fixed in 2.0.14-1.2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
raptor22.0.15-4
  • every version up to 2.0.15-4+deb12u1: fixed in 2.0.15-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
raptor2—
  • every version up to 2.0.16-6: fixed in 2.0.16-6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
raptor2—
  • every version up to 2.0.16-6: fixed in 2.0.16-6
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 28× in last 7d / 99× 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 100 of 264 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. None are among the latest 100 rows. The 164 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-57823?
CVE-2024-57823 is a critical-severity vulnerability; its CVE record was published on January 10, 2025. In Raptor RDF Syntax Library through 2.0.16, there is an integer underflow when normalizing a URI with the turtle parser in raptor_uri_normalize_path().
When was the CVE record for CVE-2024-57823 published?
The CVE record for CVE-2024-57823 was published on January 10, 2025. 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 3, 2025; the record at its source may have been updated since.
Is CVE-2024-57823 actively exploited?
CVE-2024-57823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-57823?
CVE-2024-57823 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2024-57823?
A fix for CVE-2024-57823 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-57823 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-2024-57823

Explore →

Is Your Infrastructure Affected by CVE-2024-57823?

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