CVE-2024-3119

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-04-10. NVD baseline CVSS 9.0; sources differ by 0.0.

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

Also known asEUVD-2024-31721 (ENISA EUVD) · GHSA-38jr-26cr-gjff (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.8%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Pentraze Cybersecurity) states them: "Upgrade to sngrep version 1.8.1".

A buffer overflow vulnerability exists in all versions of sngrep since v0.4.2, due to improper handling of 'Call-ID' and 'X-Call-ID' SIP headers. The functions sip_get_callid and sip_get_xcallid in sip.c use the strncpy function to copy header contents into fixed-size buffers without checking the data length. This flaw allows remote attackers to execute arbitrary code or cause a denial of service (DoS) through specially crafted SIP messages.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.8% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
1.8%
EPSS %ILE
78th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.8% 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; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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

April 10, 2024

Last Modified

February 3, 2025

Advisory Details (3)

Auto-updated Jul 26, 2026
Patch available. Sources: github_pr, github_release.
Web page

Vulnerability Reports | Pentraze Cybersecurity

https://pentraze.com/vulnerability-reports/
GitHub release Patch Available

sngrep 1.8.1

Patch available: irontec/sngrep v1.8.1

https://github.com/irontec/sngrep/releases/tag/v1.8.1
GitHub pull request Patch Available

Fixes for Stack Buffer Overflows in SIP Header Processing

Patch available: irontec/sngrep v1.8.1 (PR #480 merged 2024-04-08)

https://github.com/irontec/sngrep/pull/480/commits/73c15c82d14c69df311e05fa75da734faafd365f

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
sngrep1.4.10-1 ... 1.8.4-1 (16 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sngrep1.6.0-1 ... 1.9.0-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sngrep—
  • every version up to 1.8.1-1: fixed in 1.8.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sngrep—
  • every version up to 1.8.1-1: fixed in 1.8.1-1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-3119?
CVE-2024-3119 is a critical-severity vulnerability; its CVE record was published on April 10, 2024. A buffer overflow vulnerability exists in all versions of sngrep since v0.4.2, due to improper handling of 'Call-ID' and 'X-Call-ID' SIP headers. The functions sip_get_callid and sip_get_xcallid in sip.c use the strncpy function to copy header contents into fixed-size buffers without checking the…
When was CVE-2024-3119 made public?
CVE-2024-3119 was made public on April 9, 2024: that is the date its CVE record's CNA, Pentraze Cybersecurity, gives for when the vulnerability was made public. The CVE record itself was published on April 10, 2024. EchelonGraph's copy of the record carries a last-modified date of February 3, 2025; the record at its source may have been updated since.
Is CVE-2024-3119 actively exploited?
CVE-2024-3119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-3119?
CVE-2024-3119 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2024-3119?
A fix for CVE-2024-3119 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Pentraze Cybersecurity) states them: "Upgrade to sngrep version 1.8.1".

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-3119?

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

Book a Demo →Browse All CVEs