Vulnerability in python2.7 (DEBIAN-CVE-2019-10160)

Summary

Vulnerability in python2.7 (DEBIAN-CVE-2019-10160). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.7.16-3 or later.

Original description

The description as published by the source.

A security regression of CVE-2019-9636 was discovered in python since commit d537ab0ff9767ef024f26246899728f0116b1ec3 affecting versions 2.7, 3.5, 3.6, 3.7 and from v3.8.0a4 through v3.8.0b1, which still allows an attacker to exploit CVE-2019-9636 by abusing the user and password parts of a URL. When an application parses user-supplied URLs to store cookies, authentication credentials, or other kind of information, it is possible for an attacker to provide specially crafted URLs to make the application locate host-related information (e.g. cookies, authentication data) and send them to a different host than where it should, unlike if the URLs had been correctly parsed. The result of an attack may vary based on the application.

Source: OSV.dev (Open Source Vulnerabilities) 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 DEBIAN-CVE-2019-10160 has been found in python2.7.
Successful exploitation can lead to full system takeover.
What to do: upgrade python2.7 to 2.7.16-3 or later.
If unsure, ask your IT team or search "python2.7 DEBIAN-CVE-2019-10160" on the vendor's site.

DEBIAN-CVE-2019-10160 (python2.7)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.7.16-3 — 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 python2.7.

📍 Affected scope

Check the vendor advisory for the affected versions of python2.7.

🔥 Severity

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

🔧 How to fix

Update to 2.7.16-3.

🛡️ 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. Run grep -r 'python2.7' . 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

1
Identify exposure identify
```
grep -r 'python2.7' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で python2.7 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade python2.7 to 2.7.16-3
```
ステージング環境で 2.7.16-3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 python2.7

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.16-3"}]}]

References

advisory security-tracker.debian.org