Arbitrary Code Injection Affecting libpython3_6m1_0 package, versions <3.6.12-3.67.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.53% (77th 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 IDSNYK-SLES152-LIBPYTHON36M10-2693025
  • published14 Apr 2022
  • disclosed23 Dec 2020

Introduced: 23 Dec 2020

CVE-2019-18348  (opens in a new tab)
CWE-74  (opens in a new tab)

How to fix?

Upgrade SLES:15.2 libpython3_6m1_0 to version 3.6.12-3.67.2 or higher.

NVD Description

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

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.

References

CVSS Scores

version 3.1