Client crash via oversized authentication algorithm parameter
Published Sep 13, 2026 · Updated Sep 13, 2026
Stack buffer overflow in SIPp 3.7.7 and earlier allows remote attackers controlling a SIP server to crash the client with a crafted challenge. The createAuthHeader() function copies an oversized algorithm parameter from a 401 or 407 authentication challenge into a fixed-size stack buffer. The client must process authentication challenges from the malicious server; successful exploitation corrupts the stack and terminates the SIPp process.
Summary
What happened
Stack buffer overflow in SIPp 3.7.7 and earlier allows remote attackers controlling a SIP server to crash the client with a crafted challenge. The createAuthHeader() function copies an oversized algorithm parameter from a 401 or 407 authentication challenge into a fixed-size stack buffer. The client must process authentication challenges from the malicious server; successful exploitation corrupts the stack and terminates the SIPp process.
The record
- CVE
- CVE-2026-90779
- 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