Vulnerability in Python Software Foundation CPython (CVE-2018-1000117)

Summary

Vulnerability in Python Software Foundation CPython (CVE-2018-1000117). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.7.0 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2018-1000117 has been found in Python Software Foundation CPython.
Successful exploitation can lead to full system takeover.
What to do: upgrade Python Software Foundation CPython to 3.7.0 or later.
If unsure, ask your IT team or search "Python Software Foundation CPython CVE-2018-1000117" on the vendor's site.

CVE-2018-1000117 (Python Software Foundation CPython)
Attack vector: local / no user interaction
Patched: 3.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Python Software Foundation CPython.

📍 Affected scope

Check the vendor advisory for the affected versions of Python Software Foundation CPython.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.7.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Python Software Foundation CPython を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Python Software Foundation CPython to 3.7.0
```
ステージング環境で 3.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

patch bugs.python.org
patch github.com