Remote process crash via oversized SIP headers
Published Sep 13, 2026 · Updated Sep 13, 2026
Buffer overflow in SIP header parsing in SIPp 3.7.7 and earlier allows remote attackers to crash the process with an oversized header. The get_header() function in src/sip_parser.cpp copies more than 20,490 bytes of header content into a fixed-size buffer without enforcing its capacity. A network-reachable SIP listener requires no authentication, and successful exploitation terminates the SIPp process without reported data disclosure or code execution.
Summary
What happened
Buffer overflow in SIP header parsing in SIPp 3.7.7 and earlier allows remote attackers to crash the process with an oversized header. The get_header() function in src/sip_parser.cpp copies more than 20,490 bytes of header content into a fixed-size buffer without enforcing its capacity. A network-reachable SIP listener requires no authentication, and successful exploitation terminates the SIPp process without reported data disclosure or code execution.
The record
- CVE
- CVE-2026-90780
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- SIPp
- Product
- SIPp
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2026CVE publishedPublication date reported by the CVE source.
- Sep 13, 2026Record 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=0 <=3.7.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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