Is CVE-2018-25356 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2018-25356 being exploited in the wild.

How severe is CVE-2018-25356?

High severity, with a CVSS score of 8.4, published 23 May 2026.

Is there a fix for CVE-2018-25356?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2018-25356 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2018-25356?

Check whether you run SIPp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2018-25356: SIPp buffer overflow in command-line argument handling

CVE-2018-25356 · Severity: high · CVSS 8.4 · Published 2026-05-23

SIPp is an open-source test tool and traffic generator used to simulate network traffic for the Session Initiation Protocol (SIP). A security vulnerability in how the tool handles command-line instructions allows a local user to crash the application or potentially execute unauthorized code. This could lead to a loss of system integrity or a disruption in testing operations if an attacker has access to the machine where SIPp is running.

Technologies: SIPp. Vendors: SIPp.

Quick answers

Is CVE-2018-25356 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2018-25356 being exploited in the wild.
How severe is CVE-2018-25356?: High severity, with a CVSS score of 8.4, published 23 May 2026.
Which products and versions are affected?: SIPp 3.6 and earlier.
Is there a fix for CVE-2018-25356?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2018-25356 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2018-25356?: Check whether you run SIPp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A classic buffer overflow (CWE-120) exists in SIPp versions 3.6 and earlier due to the unsafe use of the 'strcpy' function within 'sipp.cpp'. The vulnerability is triggered when the application processes oversized input strings provided via the '-3pcc', '-i', or '-log_file' command-line parameters. Because the application fails to validate the length of these arguments before copying them into fixed-size buffers, a local attacker can overwrite adjacent memory. This can result in a denial-of-service (application crash) or arbitrary code execution with the privileges of the user running SIPp. While the vulnerability was disclosed in 2018, it was formally assigned a CVE in 2026.

Affected products

SIPp SIPp 3.6 and earlier

Timeline

2018-06-30: disclosed: Initial discovery and PoC by Fakhri Zulkifli
2018-07-02: other: Exploit-DB entry published
2026-05-23: advisory: CVE-2018-25356 published via VulnCheck/NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.