# CVE-2018-1000117: Memory corruption in n/a

> A buffer overflow in CPython's os.symlink on Windows allows arbitrary code execution and privilege escalation via crafted scripts.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9wwx-vjm7-9x2m, PSF-2022-2

## What is CVE-2018-1000117?

CVE-2018-1000117 is a medium-severity memory corruption vulnerability in Python Python, published on 7 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Python Software Foundation CPython version From 3.2 until 3.6.4 on Windows contains a Buffer Overflow vulnerability in os.symlink() function on Windows that can result in Arbitrary code execution, likely escalation of privilege. This attack appears to be exploitable via a python script that creates a symlink with an attacker controlled name or location. This vulnerability appears to have been fixed in 3.7.0 and 3.6.5.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Python Python.

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

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

## Is CVE-2018-1000117 being exploited?

There is no known exploitation of CVE-2018-1000117 in the wild and no public exploit code.

Public exploit code:

- Buffer Overflow Vulnerability that can result ACE (github_poc): https://github.com/u0pattern/CVE-2018-1000117-Exploit

## Other vulnerabilities in Python Python

- [CVE-2008-5031](https://insights.sbomify.com/CVE-2008-5031/): Integer overflow in n/a (critical 10.0)
- [CVE-2014-4650](https://insights.sbomify.com/CVE-2014-4650/): Path traversal in n/a (critical 9.8)
- [CVE-2016-5636](https://insights.sbomify.com/CVE-2016-5636/): Integer overflow in n/a (critical 9.8)
- [CVE-2007-4559](https://insights.sbomify.com/CVE-2007-4559/): Path traversal in n/a (critical 9.8)
- [CVE-2017-17522](https://insights.sbomify.com/CVE-2017-17522/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000117 is a medium-severity memory corruption vulnerability in Python Python, published on 7 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000117 in the wild and no public exploit code.

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

## Sources

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

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