# CVE-2024-35434: Memory corruption in n/a

> Attackers can cause a denial of service in Sngrep by sending a crafted SIP packet that triggers a heap buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 29 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2024-35434, UBUNTU-CVE-2024-35434, openSUSE-SU-2024:14057-1

## What is CVE-2024-35434?

CVE-2024-35434 is a high-severity memory corruption vulnerability in n/a, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Irontec Sngrep v1.8.1 was discovered to contain a heap buffer overflow via the function rtp_check_packet at /sngrep/src/rtp.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SIP packet.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sngrep` | openSUSE:Tumbleweed | All versions | 1.8.1-2.1 |

Products: Irontec Sngrep.

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

Apply the vendor's patch.

## Is CVE-2024-35434 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35434 exists.

## Other vulnerabilities in n/a

- [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-2024-3120](https://insights.sbomify.com/CVE-2024-3120/): Stack-Buffer Overflow in 'Content-Length' and 'Warning' 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35434 is a high-severity memory corruption vulnerability in n/a, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35434 exists.

Affected product: n/a. 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-35434/ (Markdown: https://insights.sbomify.com/CVE-2024-35434/index.md)
```

## Sources

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

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