CVE-2024-3120: Stack-Buffer Overflow in 'Content-Length' and 'Warning' Header Processing in sngrep
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: sngrep (Debian:13) 1.8.1-1; sngrep (openSUSE:Leap 15.5) 1.8.1-bp155.2.3.1; sngrep (openSUSE:Tumbleweed) 1.8.1-1.1.
Add it to your regular patch cycle. Upgrade to sngrep (Debian:13) 1.8.1-1; sngrep (openSUSE:Leap 15.5) 1.8.1-bp155.2.3.1; sngrep (openSUSE:Tumbleweed) 1.8.1-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A stack-buffer overflow vulnerability exists in all versions of sngrep since v1.4.1. The flaw is due to inadequate bounds checking when copying 'Content-Length' and 'Warning' headers into fixed-size buffers in the sip_validate_packet and sip_parse_extra_headers functions within src/sip.c. This vulnerability allows remote attackers to execute arbitrary code or cause a denial of service (DoS) via crafted SIP messages.
- Published
- Apr 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 79th percentile
- CWE
- CWE-120
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · Pentraze
- 9.0
- 0.8 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| irontec | sngrep | cpe:2.3:a:irontec:sngrep |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Pentraze). Independent of NVD's CPE analysis and usually ahead of it.
irontec sngrep
- 1.4.1 and later · up to and including 1.8.0affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- irontec sngrep1.4.1 and later · before 1.8.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | sngrep | from 0 | — |
| Debian:13 | sngrep | before 1.8.1-1 | 1.8.1-1 |
| openSUSE:Leap 15.5 | sngrep | before 1.8.1-bp155.2.3.1 | 1.8.1-bp155.2.3.1 |
| openSUSE:Tumbleweed | sngrep | before 1.8.1-1.1 | 1.8.1-1.1 |
| SUSE:Package Hub 15 SP5 | sngrep | before 1.8.1-bp155.2.3.1 | 1.8.1-bp155.2.3.1 |
Same product
irontec: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-3119Stack-Buffer Overflow in 'Call-ID' and 'X-Call-ID' SIP Header Processing in sngrep40Plan
- CVE-2026-90558sngrep through 1.8.4 Stack Buffer Overflow via SIP Headers37Monitor
- CVE-2023-36192Sngrep v1.6.0 was discovered to contain a heap buffer overflow via the function capture_ws_check_packet at /src/capture.c.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-31981May 9, 2023 · Sngrep v1.6.0 was discovered to contain a stack buffer overflow via the function packet_set_payload at /src/packet.c.31Monitor
- ← EarlierCVE-2023-31982May 9, 2023 · Sngrep v1.6.0 was discovered to contain a heap buffer overflow via the function capture_packet_reasm_ip at /src/capture.c.31Monitor
- Later →CVE-2024-35434May 29, 2024 · Irontec Sngrep v1.8.1 was discovered to contain a heap buffer overflow via the function rtp_check_packet at /sngrep/src/rtp.c.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:sngrep | 1.8.1-1 · Debian:13 | Package registry (OSV) |
| opensuse:sngrep | 1.8.1-bp155.2.3.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:sngrep | 1.8.1-bp155.2.3.1 · SUSE:Package Hub 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-31190 days apartStack-Buffer Overflow in 'Call-ID' and 'X-Call-ID' SIP Header Processing in sngrep40Plan
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.