Remote code execution via unchecked SIP header copies
Published Apr 9, 2024 · Updated Feb 21, 2025
Stack-buffer overflow in Irontec sngrep 1.4.1 through 1.8.0 allows remote attackers to execute code or crash the process via crafted SIP messages. In sip_validate_packet and sip_parse_extra_headers, match lengths from Content-Length and Warning headers drive strncpy into fixed-size stack buffers without bounds checks. Processing an attacker-controlled SIP packet during live capture or PCAP viewing is sufficient; successful exploitation grants code execution, while failed attempts can terminate the viewer.
Summary
What happened
Stack-buffer overflow in Irontec sngrep 1.4.1 through 1.8.0 allows remote attackers to execute code or crash the process via crafted SIP messages. In sip_validate_packet and sip_parse_extra_headers, match lengths from Content-Length and Warning headers drive strncpy into fixed-size stack buffers without bounds checks. Processing an attacker-controlled SIP packet during live capture or PCAP viewing is sufficient; successful exploitation grants code execution, while failed attempts can terminate the viewer.
The record
- CVE
- CVE-2024-3120
- Published
- Apr 9, 2024
- Updated
- Feb 21, 2025
- Vendor
- Irontec
- Product
- sngrep
- Classifications
- CWE-120, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.4.1 <=1.8.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted Content-Length SIP message reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo