CRLF Injection Affecting python2-urllib3 package, versions <1.22-6.4.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
6.47% (91st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about CRLF Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-SLES150-PYTHON2URLLIB3-2737888
  • published14 Apr 2022
  • disclosed9 Sept 2019

Introduced: 9 Sep 2019

CVE-2019-9740  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 python2-urllib3 to version 1.22-6.4.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python2-urllib3 package and not the python2-urllib3 package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

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 query string after a ? character) followed by an HTTP header or a Redis command. 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.

References

CVSS Base Scores

version 3.1