Unauthenticated crash via oversized SIP To tag
Published Sep 13, 2026 · Updated Sep 13, 2026
Buffer overflow in SIPp through 3.7.7 allows remote attackers to crash the process via SIP To headers with oversized tag parameters. The get_peer_tag() function copies tag values of at least 2049 bytes into a fixed static buffer without sufficient bounds enforcement. The unauthenticated network path requires only a crafted SIP message and results in process termination, with no supported evidence of data disclosure or code execution.
Summary
What happened
Buffer overflow in SIPp through 3.7.7 allows remote attackers to crash the process via SIP To headers with oversized tag parameters. The get_peer_tag() function copies tag values of at least 2049 bytes into a fixed static buffer without sufficient bounds enforcement. The unauthenticated network path requires only a crafted SIP message and results in process termination, with no supported evidence of data disclosure or code execution.
The record
- CVE
- CVE-2026-90778
- Published
- Sep 13, 2026
- Updated
- Sep 13, 2026
- Vendor
- SIPp
- Product
- SIPp
- Classifications
- T1499.004
- 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