CVE-2024-3120

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-04-10 00:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.8% in the next 30 days (EPSS).
• Severity: 9.0 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-04-10 00:15 UTC

Last modified

2026-06-17 07:43 UTC

Exploit probability

1.8% · EPSS, next 30 days

Weakness

CWE-120 · Classic buffer overflow

Record status

Analyzed

Affected

• Irontec Sngrep < 1.8.1

Attack profile CVSS 3.1 · 9.0

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-3120.md and follow it. Check whether this project is affected by CVE-2024-3120. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge