CVE-2024-52949

CRITICALNVD 7.59.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-12-17. NVD baseline CVSS 7.5; sources differ by 2.3.

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

Also known asEUVD-2024-46264 (ENISA EUVD) · GHSA-94mp-gc2x-rqm6 (GitHub Security Advisories)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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

iptraf-ng 1.2.1 has a stack-based buffer overflow. In src/ifaces.c, the strcpy function consistently fails to control the size, and it is consequently possible to overflow memory on the stack.

CVSS v3
7.5
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
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.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 public PoC (CISA Vulnrichment) · Automatable yes (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)14 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 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

December 16, 2024

Last Modified

October 14, 2025

Advisory Details (2)

Auto-updated Oct 14, 2026
Patch available. Sources: github_release.
Web page

Gruppo TIM | Vulnerability Research & Advisor

https://www.gruppotim.it/it/footer/red-team.html
GitHub release Patch Available

Version 1.2.1

Patch available: iptraf-ng/iptraf-ng v1.2.1

https://github.com/iptraf-ng/iptraf-ng/releases/tag/v1.2.1

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatiptraf-ng-0:1.2.2-1.el92025-05-13redhat

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
iptraf-ng1:1.2.1-1, 1:1.2.1-2, 1:1.2.2-1
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
iptraf-ng1:1.2.1-1, 1:1.2.1-2, 1:1.2.2-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
iptraf-ng1:1.2.1-2, 1:1.2.2-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
iptraf-ng1:1.2.1-2
  • every version up to 1:1.2.2-1: fixed in 1:1.2.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2024-52949?
CVE-2024-52949 is a critical-severity vulnerability; its CVE record was published on December 16, 2024. iptraf-ng 1.2.1 has a stack-based buffer overflow. In src/ifaces.c, the strcpy function consistently fails to control the size, and it is consequently possible to overflow memory on the stack.
When was the CVE record for CVE-2024-52949 published?
The CVE record for CVE-2024-52949 was published on December 16, 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 October 14, 2025; the record at its source may have been updated since.
Is CVE-2024-52949 actively exploited?
CVE-2024-52949 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52949?
CVE-2024-52949 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2024-52949?
A fix for CVE-2024-52949 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-52949 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-52949

Explore →

Is Your Infrastructure Affected by CVE-2024-52949?

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