Process crash via uninitialized message state
Published Jan 23, 2026 · Updated Jan 23, 2026
NULL pointer dereference in SIPp 3.7.3 allows remote attackers to crash the process with crafted SIP messages during an active call. SendingMessage leaves pointer and state members uninitialized, allowing malformed message structures to drive a NULL dereference. Exploitation requires message replay during an active call; arbitrary code execution is reported only under unspecified memory-layout and runtime conditions.
Summary
What happened
NULL pointer dereference in SIPp 3.7.3 allows remote attackers to crash the process with crafted SIP messages during an active call. SendingMessage leaves pointer and state members uninitialized, allowing malformed message structures to drive a NULL dereference. Exploitation requires message replay during an active call; arbitrary code execution is reported only under unspecified memory-layout and runtime conditions.
The record
- CVE
- CVE-2026-0710
- Published
- Jan 23, 2026
- Updated
- Jan 23, 2026
- Vendor
- SIPp
- Product
- SIPp
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2026CVE publishedPublication date reported by the CVE source.
- Jan 23, 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=3.7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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