CRLF Injection Affecting python27:2.7/python2-pyyaml package, versions <0:3.12-16.module_el8.6.0+2781+fed64c13


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.4% (74th 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-ALMALINUX8-PYTHON27-5635198
  • published28 May 2023
  • disclosed5 Nov 2019

Introduced: 5 Nov 2019

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

How to fix?

Upgrade AlmaLinux:8 python27:2.7/python2-pyyaml to version 0:3.12-16.module_el8.6.0+2781+fed64c13 or higher.
This issue was patched in ALSA-2019:3335.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27:2.7/python2-pyyaml package and not the python27:2.7/python2-pyyaml package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 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 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.

References

CVSS Scores

version 3.1