ghsa-89ff-5r66-wr8j
Vulnerability from github
Published
2022-05-13 01:11
Modified
2022-05-13 01:11
Severity ?
Details
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.
{ "affected": [], "aliases": [ "CVE-2019-9947" ], "database_specific": { "cwe_ids": [ "CWE-93" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2019-03-23T18:29:00Z", "severity": "MODERATE" }, "details": "An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \\r\\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.", "id": "GHSA-89ff-5r66-wr8j", "modified": "2022-05-13T01:11:47Z", "published": "2022-05-13T01:11:47Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-9947" }, { "type": "WEB", "url": "https://usn.ubuntu.com/4127-2" }, { "type": "WEB", "url": "https://usn.ubuntu.com/4127-1" }, { "type": "WEB", "url": "https://security.netapp.com/advisory/ntap-20190404-0004" }, { "type": "WEB", "url": "https://security.gentoo.org/glsa/202003-26" }, { "type": "WEB", "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JXASHCDD4PQFKTMKQN4YOP5ZH366ABN4" }, { "type": "WEB", "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMWSKTNOHSUOT3L25QFJAVCFYZX46FYK" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2020/08/msg00034.html" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2020/07/msg00011.html" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2019/06/msg00026.html" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2019/06/msg00023.html" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2019/06/msg00022.html" }, { "type": "WEB", "url": "https://bugs.python.org/issue35906" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2019:3725" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2019:3520" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2019:3335" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2019:2030" }, { "type": "WEB", "url": "https://access.redhat.com/errata/RHSA-2019:1260" }, { "type": "WEB", "url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00062.html" }, { "type": "WEB", "url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00063.html" }, { "type": "WEB", "url": "http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html" }, { "type": "WEB", "url": "http://www.openwall.com/lists/oss-security/2021/02/04/2" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ] }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.