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

Published Apr 9, 2024
·
Updated

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 sipvalidatepacket and sipparseextraheaders 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.

Affected Software

2 affected components
Irontec Sngrep>=1.4.1<1.8.1
sngrep sngrep>=1.4.1

Remediation

Information

Upgrade to sngrep version 1.8.1

Event History

Apr 9, 2024
CVE Published
via MITRE·11:55 PM
Data Sourced
via MITRE·11:55 PM
RemedyDescriptionSeverityWeakness
Apr 10, 2024
Data Sourced
via NVD·12:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 9, 57065
Event
via NVD·03:32 AM

Frequently Asked Questions

1

What is the severity of CVE-2024-3120?

CVE-2024-3120 is classified as a high-severity vulnerability due to the potential for remote code execution caused by a stack-buffer overflow.

2

How do I fix CVE-2024-3120?

To fix CVE-2024-3120, update sngrep to version 1.8.1 or later, which includes the necessary security patches.

3

What are the affected versions of sngrep for CVE-2024-3120?

All versions of sngrep from 1.4.1 to 1.8.0 are affected by CVE-2024-3120.

4

What functions are vulnerable in CVE-2024-3120?

The vulnerable functions in CVE-2024-3120 are sip_validate_packet and sip_parse_extra_headers due to insufficient bounds checking.

5

Can CVE-2024-3120 be exploited remotely?

Yes, CVE-2024-3120 can be exploited remotely if an attacker sends specially crafted packets that trigger the stack-buffer overflow.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203