Algorithmic Complexity Affecting python39:3.9/python39-pyyaml package, versions <0:5.4.1-1.module_el8.6.0+2780+a40f65e1


Severity

Recommended
medium

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.79% (82nd 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-ALMALINUX8-PYTHON39-5651629
  • published28 May 2023
  • disclosed28 Feb 2023

Introduced: 28 Feb 2023

CVE-2022-45061  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 python39:3.9/python39-pyyaml to version 0:5.4.1-1.module_el8.6.0+2780+a40f65e1 or higher.
This issue was patched in ALSA-2023:2764.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python39:3.9/python39-pyyaml package and not the python39:3.9/python39-pyyaml package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

References

CVSS Scores

version 3.1