Code Injection in openapi-python-client (CVE-2020-15142)
Summary
Code injection in openapi-python-client (CVE-2020-15142). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.5.3 or later.
Original description
The description as published by the source.
Impact
Clients generated with a maliciously crafted OpenAPI Document can generate arbitrary Python code. Subsequent execution of this malicious client is arbitrary code execution.
Giving this a CVSS of 8.0 (high) with CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H/E:P/RL:U/RC:C .
Patches
Fix will be included in version 0.5.3
Workarounds
Inspect OpenAPI documents before generating, or inspect generated code before executing.
For more information
If you have any questions or comments about this advisory:
- Open an issue in openapi-python-client
- Email us at danthony@triaxtec.com
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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-2020-15142 has been found in openapi-python-client.
Successful exploitation can lead to full system takeover.
What to do: upgrade openapi-python-client to 0.5.3 or later.
If unsure, ask your IT team or search "openapi-python-client CVE-2020-15142" on the vendor's site.
CVE-2020-15142 (openapi-python-client) — CWE-94
Attack vector: remote (network-reachable)
Patched: 0.5.3 — apply immediately
Workaround: Inspect OpenAPI documents before generating, or inspect generated code before executing.
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.
Arbitrary code execution (CWE-94) exists in openapi-python-client.
Check the vendor advisory for the affected versions of openapi-python-client.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.5.3.
Workaround: Inspect OpenAPI documents before generating, or inspect generated code before executing.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openapi-python-client' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openapi-python-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openapi-python-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Inspect OpenAPI documents before generating, or inspect generated code before executing.パッチが適用されるまでの応急処置として、Inspect OpenAPI documents before generating, or inspect generated code before executing. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade openapi-python-client to 0.5.3ステージング環境で 0.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web pypi.org