You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
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.
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
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 arbitrary code on the system by abusing the python/object/new constructor.
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
mend-local-appbot
changed the title
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8)
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) - autoclosed
Oct 10, 2024
mend-local-appbot
changed the title
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) - autoclosed
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) unreachable
Oct 15, 2024
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.
mend-local-appbot
changed the title
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) unreachable
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) reachable
Oct 16, 2024
mend-local-appbot
changed the title
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) reachable
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8)
Oct 30, 2024
mend-local-appbot
changed the title
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8)
PyYAML-3.13.tar.gz: 2 vulnerabilities (highest severity is: 9.8) reachable
Oct 30, 2024
Vulnerable Library - PyYAML-3.13.tar.gz
YAML parser and emitter for Python
Library home page: https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz
Path to dependency file: /requirements.txt
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
Found in HEAD commit: 09bc0f8a17090dbee6aea6ae77fd0bc7a492f6a0
Vulnerabilities
Reachable
Unreachable
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2017-18342
Vulnerable Library - PyYAML-3.13.tar.gz
YAML parser and emitter for Python
Library home page: https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz
Path to dependency file: /requirements.txt
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
Dependency Hierarchy:
Found in HEAD commit: 09bc0f8a17090dbee6aea6ae77fd0bc7a492f6a0
Found in base branch: master
Reachability Analysis
This vulnerability is potentially reachable
Vulnerability Details
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.
Publish Date: 2018-06-27
URL: CVE-2017-18342
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://nvd.nist.gov/vuln/detail/CVE-2017-18342
Release Date: 2018-06-27
Fix Resolution: PyYAML - 5.1
In order to enable automatic remediation, please create workflow rules
CVE-2020-1747
Vulnerable Library - PyYAML-3.13.tar.gz
YAML parser and emitter for Python
Library home page: https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz
Path to dependency file: /requirements.txt
Path to vulnerable library: /private/var/folders/y1/nn9dz5v14q51wqskf74gr9w40000gr/T/ws-ua_20241030114039_TXODRV/python_ZQGPHY/202410301140391/env/lib/python3.9/site-packages/PyYAML-3.13.dist-info
Dependency Hierarchy:
Found in HEAD commit: 09bc0f8a17090dbee6aea6ae77fd0bc7a492f6a0
Found in base branch: master
Reachability Analysis
The vulnerable code is unreachable
Vulnerability Details
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 arbitrary code on the system by abusing the python/object/new constructor.
Publish Date: 2020-03-24
URL: CVE-2020-1747
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1747
Release Date: 2020-03-24
Fix Resolution: 5.3.1
In order to enable automatic remediation, please create workflow rules
In order to enable automatic remediation for this issue, please create workflow rules
The text was updated successfully, but these errors were encountered: