# CVE-2018-25222: SC v7.16 Stack-Based Buffer Overflow Remote Code Execution

> Local attackers can execute arbitrary code via a stack-based buffer overflow in SC by supplying oversized input strings.

- **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:** DEBIAN-CVE-2018-25222, GHSA-g5hv-3r2w-5ch9, UBUNTU-CVE-2018-25222

## What is CVE-2018-25222?

CVE-2018-25222 is a high-severity memory corruption vulnerability in SC, 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

SC v7.16 contains a stack-based buffer overflow vulnerability that allows local attackers to execute arbitrary code by supplying oversized input that exceeds buffer boundaries. Attackers can craft malicious input strings exceeding 1052 bytes to overwrite the instruction pointer and execute shellcode in the application context.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2018-25222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25222 is a high-severity memory corruption vulnerability in SC, 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-25222 exists.

Affected product: SC. 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-25222/ (Markdown: https://insights.sbomify.com/CVE-2018-25222/index.md)
```

## Sources

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

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