dbcve.org
PythonApplication

CVE-2019-10160

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-07
Fix available
A fix is available. Upgrade to 2.7.17 / 3.5.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PythonApplication
Affected:>= 2.7.0, < 2.7.17>= 3.5.0, < 3.5.8>= 3.6.0, < 3.6.9>= 3.7.0, < 3.7.4= 3.8.0
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux EusOperating system
Affected:= 7.6
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.6
Enterprise Linux Server TusOperating system
Affected:= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 7.0
Debian LinuxOperating system
Affected:= 8.0= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.17 / 3.5.8 / 3.6.9 or later
Fixed in 2.7.173.5.83.6.9
Vendor patch bugzilla.redhat.com →
Recommended fix High confidence

Python 2.7.17+, Python 3.5.8+, Python 3.6.9+, or Python 3.7.4+ depending on your major version branch

  1. 1. Identify the current Python version in your environment using `python --version` or `python3 --version`
  2. 2. For Python 2.7.x: Upgrade to Python 2.7.17 or later
  3. 3. For Python 3.5.x: Upgrade to Python 3.5.8 or later
  4. 4. For Python 3.6.x: Upgrade to Python 3.6.9 or later
  5. 5. For Python 3.7.x: Upgrade to Python 3.7.4 or later
  6. 6. On RHEL/CentOS systems, run `sudo yum update python` or `sudo dnf update python` to apply security updates
  7. 7. On Debian/Ubuntu systems, run `sudo apt-get update && sudo apt-get upgrade python3`
  8. 8. Verify the fix by checking the new Python version and ensuring it matches or exceeds the fixed versions listed above
Caveat Minor/Patch releases typically have low risk, but test thoroughly as with any upgrade; Python 2.7 reached end-of-life in 2020, consider migrating to Python 3 if still on 2.7

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10160 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data