CVE-2024-25110

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 7.3% (94th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-22471 (ENISA EUVD)Source: ENISA EUVD

9.8EG
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 severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 7.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The UAMQP is a general purpose C library for AMQP 1.0. During a call to open_get_offered_capabilities, a memory allocation may fail causing a use-after-free issue and if a client called it during connection communication it may cause a remote code execution. Users are advised to update the submodule with commit 30865c9c. There are no known workarounds for this vulnerability.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
62
EG Risk 62/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation7.3% × 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 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
7.3%
EPSS %ILE
94th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
7.3% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; 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 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)3 days if the affected system is publicly exposed; 60 days if it is not.

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

February 12, 2024

Last Modified

November 22, 2024

Advisory Details (2)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Azure IoT Platform Device SDK Remote Code Execution Vulnerability · Advisory · Azure/azure-uamqp-c · GitHub

https://github.com/Azure/azure-uamqp-c/security/advisories/GHSA-c646-4whf-r67v
GitHub commit

commit 30865c9cceda (Azure/azure-uamqp-c)

Fix landed in Azure/azure-uamqp-c commit 30865c9cceda — awaiting tagged release

https://github.com/Azure/azure-uamqp-c/commit/30865c9ccedaa32ddb036e87a8ebb52c3f18f695

Vendor Advisories for CVE-2024-25110(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python1.2.13-1 ... 1.6.9-3 (21 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python1.5.3-1 ... 1.6.9-3 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python—
  • every version up to 1.6.8-2: fixed in 1.6.8-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
azure-uamqp-python—
  • every version up to 1.6.8-2: fixed in 1.6.8-2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 265 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 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-25110?
CVE-2024-25110 is a critical-severity vulnerability; its CVE record was published on February 12, 2024. The UAMQP is a general purpose C library for AMQP 1.0. During a call to open_get_offered_capabilities, a memory allocation may fail causing a use-after-free issue and if a client called it during connection communication it may cause a remote code execution. Users are advised to update the…
When was the CVE record for CVE-2024-25110 published?
The CVE record for CVE-2024-25110 was published on February 12, 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 22, 2024; the record at its source may have been updated since.
Is CVE-2024-25110 actively exploited?
CVE-2024-25110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.3% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-25110?
CVE-2024-25110 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-25110?
A fix for CVE-2024-25110 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-25110 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-25110

Explore →

Is Your Infrastructure Affected by CVE-2024-25110?

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