Local code execution via unchecked argument copies
Published May 23, 2026 · Updated May 23, 2026
Buffer overflow in SIPp 3.6 and earlier allows local attackers to crash the application or execute arbitrary code through crafted arguments. The 3PCC, IP-address, and log-file option handlers in sipp.cpp pass oversized command-line values to strcpy without checking destination-buffer bounds. Local command-line access is required; successful exploitation either terminates the SIP traffic generator or runs code in the SIPp process context.
Summary
What happened
Buffer overflow in SIPp 3.6 and earlier allows local attackers to crash the application or execute arbitrary code through crafted arguments. The 3PCC, IP-address, and log-file option handlers in sipp.cpp pass oversized command-line values to strcpy without checking destination-buffer bounds. Local command-line access is required; successful exploitation either terminates the SIP traffic generator or runs code in the SIPp process context.
The record
- CVE
- CVE-2018-25356
- Published
- May 23, 2026
- Updated
- May 23, 2026
- Vendor
- SIPp
- Product
- SIPp
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 23, 2026CVE publishedPublication date reported by the CVE source.
- May 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=0 <=3.6
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
- SIPp 3.6 - Local Buffer Overflow (PoC)proof 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