Debian Pyyaml vulnerabilities

5 known vulnerabilities affecting debian/pyyaml.

Total CVEs
5
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL2MEDIUM1LOW2

Vulnerabilities

Page 1 of 1
CVE-2020-1747CRITICALCVSS 9.8fixed in pyyaml 5.3-2 (bookworm)2020
CVE-2020-1747 [CRITICAL] CVE-2020-1747: pyyaml - A vulnerability was discovered in the PyYAML library in versions before 5.3.1, w... A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. An attacker could use this flaw to execute a
debian
CVE-2020-14343CRITICALCVSS 9.8fixed in pyyaml 5.3.1-4 (bookworm)2020
CVE-2020-14343 [CRITICAL] CVE-2020-14343: pyyaml - A vulnerability was discovered in the PyYAML library in versions before 5.4, whe... A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbi
debian
CVE-2019-20477LOWCVSS 9.8fixed in pyyaml 5.2-1 (bookworm)2019
CVE-2019-20477 [CRITICAL] CVE-2019-20477: pyyaml - PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all ... PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342. Scope: local bookworm: resolved (fixed in 5.2-1) bullseye: resolved (fixed in 5.2-1) forky: resolved (fixed in
debian
CVE-2017-18342LOWCVSS 9.8fixed in pyyaml 5.1.2-1 (bookworm)2017
CVE-2017-18342 [CRITICAL] CVE-2017-18342: pyyaml - In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used w... In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the 'UnsafeLoader' has been introduced for backward compatibility with the function. Scope: local bookworm: resolved (fixed in 5.1.2-1) bullseye: resolved (fixed in 5.1.2-1) forky: resolved (fixed in 5.1.2-
debian
CVE-2014-9130MEDIUMCVSS 5.0fixed in libyaml 0.1.6-3 (bookworm)2014
CVE-2014-9130 [MEDIUM] CVE-2014-9130: libyaml - scanner.c in LibYAML 0.1.5 and 0.1.6, as used in the YAML-LibYAML (aka YAML-XS) ... scanner.c in LibYAML 0.1.5 and 0.1.6, as used in the YAML-LibYAML (aka YAML-XS) module for Perl, allows context-dependent attackers to cause a denial of service (assertion failure and crash) via vectors involving line-wrapping. Scope: local bookworm: resolved (fixed in 0.1.6-3) bullseye: resolved (fixed in 0.1.6-3) forky: resolved (fixed in 0.1.6-3) sid: resolved (f
debian