Name | CVE-2019-18348 |
Description | An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. 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 host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
References | DLA-2280-1, ELA-239-1 |
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|---|---|---|
python2.7 (PTS) | jessie, jessie (lts) | 2.7.9-2-ds1-1+deb8u12 | vulnerable |
stretch (security) | 2.7.13-2+deb9u6 | vulnerable | |
stretch (lts), stretch | 2.7.13-2+deb9u9 | vulnerable | |
buster (security), buster, buster (lts) | 2.7.16-2+deb10u4 | vulnerable | |
bullseye | 2.7.18-8+deb11u1 | fixed | |
python3.4 (PTS) | jessie, jessie (lts) | 3.4.2-1+deb8u19 | fixed |
python3.5 (PTS) | stretch (security) | 3.5.3-1+deb9u5 | fixed |
stretch (lts), stretch | 3.5.3-1+deb9u11 | fixed | |
python3.7 (PTS) | buster, buster (lts) | 3.7.3-2+deb10u9 | vulnerable |
buster (security) | 3.7.3-2+deb10u7 | vulnerable |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|---|---|---|---|---|---|
python2.7 | source | (unstable) | 2.7.18~rc1-1 | unimportant | ||
python3.4 | source | jessie | 3.4.2-1+deb8u8 | ELA-239-1 | ||
python3.4 | source | (unstable) | (unfixed) | unimportant | ||
python3.5 | source | stretch | 3.5.3-1+deb9u2 | DLA-2280-1 | ||
python3.5 | source | (unstable) | (unfixed) | unimportant | ||
python3.7 | source | (unstable) | (unfixed) | unimportant | ||
python3.8 | source | (unstable) | 3.8.3~rc1-1 | unimportant |
https://github.com/python/cpython/commit/9165addc22d05e776a54319a8531ebd0b2fe01ef (master)
https://github.com/python/cpython/commit/ff69c9d12c1b06af58e5eae5db4630cedd94740e (3.8 branch)
https://github.com/python/cpython/commit/34f85af3229f86c004a954c3f261ceea1f5e9f95 (3.7 branch)
https://github.com/python/cpython/commit/09d8172837b6985c4ad90ee025f6b5a554a9f0ac (3.5 branch)
https://github.com/python/cpython/commit/e176e0c105786e9f476758eb5438c57223b65e7f (v2.7.18rc1)
https://bugs.python.org/issue38576
Issue only exploitable if CVE-2016-10739 is unfixed in src:glibc. This is
not the case in all suites, but the issue is minor in general and would
tend to a no-dsa/ignored tag in those suites.