CVE-2019-10160
No exploitation reported by the sources we read.
- Published2019-06-07
- WeaknessCWE-172 · CWE-522
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2019-06-0718:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-10160?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-10160?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 18.4 | = 18.04 | no fix published | NVD |
| 19.4 | = 19.04 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.7 | ≥ 3.7.0, < 3.7.4 | 3.7.4 | NVD |
| 3.6 | ≥ 3.6.0, < 3.6.9 | 3.6.9 | NVD |
| 3.5 | ≥ 3.5.0, < 3.5.8 | 3.5.8 | NVD |
| 2.7 | ≥ 2.7.0, < 2.7.17 | 2.7.17 | NVD |
| 3.8 | = 3.8.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 29.x | = 29 | no fix published | NVD |
| 30.x | = 30 | no fix published | NVD |
| 31.x | = 31 | no fix published | NVD |
11 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- bugzilla.redhat.comPatch
- github.comPatch
- github.comPatch
- github.comPatch
- github.comPatch
- python-security.readthedocs.ioPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-06-07
- Last Modified
- 2026-10-14
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-10160?
Is CVE-2019-10160 actively exploited?
What is the CVSS score for CVE-2019-10160?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.