# CVE-2018-25225: SIPP 3.3 Stack-Based Buffer Overflow via Configuration File

> Local attackers can execute arbitrary code by providing a malicious configuration file to SIPP, a SIP performance testing tool.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-36cw-x2xf-xmg3

## What is CVE-2018-25225?

CVE-2018-25225 is a high-severity memory corruption vulnerability in SIPP, published on 28 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SIPP 3.3 contains a stack-based buffer overflow vulnerability that allows local unauthenticated attackers to execute arbitrary code by supplying malicious input in the configuration file. Attackers can craft a configuration file with oversized values that overflow a stack buffer, overwriting the return address and executing arbitrary code through return-oriented programming gadgets.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-25225?

It affects 1 product.


Products: Sipp Project Sipp.

## How do I fix CVE-2018-25225?

No fix has been published for CVE-2018-25225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25225 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25225 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25225 and fix it if it is affected.

What it is: CVE-2018-25225 is a high-severity memory corruption vulnerability in SIPP, published on 28 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25225 exists.

Affected product: SIPP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25225/ (Markdown: https://insights.sbomify.com/CVE-2018-25225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25225
- OSV: https://osv.dev/vulnerability/CVE-2018-25225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25225/
Summaries are generated and may contain mistakes; the official description above is the record.