# CVE-2024-3120: Stack-Buffer Overflow in 'Content-Length' and 'Warning' Header Processing in sngrep

> Remote attackers can execute arbitrary code or cause denial of service in sngrep via crafted SIP messages exploiting stack buffer overflows.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2024
- **Updated:** 21 Feb 2025
- **Also known as:** DEBIAN-CVE-2024-3120, GHSA-4p8q-p8qc-486x, UBUNTU-CVE-2024-3120

## What is CVE-2024-3120?

CVE-2024-3120 is a critical memory corruption vulnerability in irontec sngrep, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-3120?

It affects 1 product.


Products: Irontec Sngrep.

## How do I fix CVE-2024-3120?

Upgrade to a fixed version.

## Is CVE-2024-3120 being exploited?

There is no known exploitation of CVE-2024-3120 in the wild and no public exploit code.

## Other vulnerabilities in irontec sngrep

- [CVE-2024-3119](https://insights.sbomify.com/CVE-2024-3119/): Stack-Buffer Overflow in 'Call-ID' and 'X-Call-ID' SIP Header Processing in sngrep (critical 9.0)
- [CVE-2023-36192](https://insights.sbomify.com/CVE-2023-36192/): Memory corruption in n/a (high 7.8)
- [CVE-2023-31981](https://insights.sbomify.com/CVE-2023-31981/): Memory corruption in n/a (high 7.8)
- [CVE-2023-31982](https://insights.sbomify.com/CVE-2023-31982/): Memory corruption in n/a (high 7.8)
- [CVE-2024-35434](https://insights.sbomify.com/CVE-2024-35434/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3120 and fix it if it is affected.

What it is: CVE-2024-3120 is a critical memory corruption vulnerability in irontec sngrep, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3120 in the wild and no public exploit code.

Affected product: irontec sngrep. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3120/ (Markdown: https://insights.sbomify.com/CVE-2024-3120/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3120
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3120
- OSV: https://osv.dev/vulnerability/CVE-2024-3120

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3120/
Summaries are generated and may contain mistakes; the official description above is the record.