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.

The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-9341 advisory.

  - In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with two     content-length headers, it ignored the first header. When the second content-length value was set to zero,     the request body was interpreted as a pipelined request. (CVE-2020-10108)

  - In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with a     content-length and a chunked encoding header, the content-length took precedence and the remainder of the     request body was interpreted as a pipelined request. (CVE-2020-10109)

  - A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly     imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote     attacker could exploit this flaw to run arbitrary HTML/JS code. (CVE-2020-27783)

  - 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. (CVE-2017-18342)

  - Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via     django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of     arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by     application developers to also show file contents, then not only the existence but also the file contents     would have been exposed. In other words, there is directory traversal outside of the template root     directories. (CVE-2021-33203)

  - In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address,     and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a     bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address     are unaffected with Python 3.9.5+..) . (CVE-2021-33571)

  - In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with     trailing newlines could bypass upstream access control based on URL paths. (CVE-2021-44420)

  - In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and     FieldFile allowed directory traversal via uploaded files with suitably crafted file names.
    (CVE-2021-31542)

  - In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory     traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected     by this vulnerability. (CVE-2021-28658)

  - lxml is a library for processing XML and HTML in the Python language. Prior to version 4.6.5, the HTML     Cleaner in lxml.html lets certain crafted script content pass through, as well as script content in SVG     files embedded using data URIs. Users that employ the HTML cleaner in a security relevant context should     upgrade to lxml 4.6.5 to receive a patch. There are no known workarounds available. (CVE-2021-43818)

  - An XSS vulnerability was discovered in python-lxml's clean module versions before 4.6.3. When disabling     the safe_attrs_only and forms arguments, the Cleaner class does not remove the formaction attribute     allowing for JS to bypass the sanitizer. A remote attacker could exploit this flaw to run arbitrary JS     code on users who interact with incorrectly sanitized HTML. This issue is patched in lxml 4.6.3.
    (CVE-2021-28957)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202003-45 (PyYAML: Arbitrary code execution)

    It was found that using yaml.load() API on untrusted input could lead to       arbitrary code execution.
  Impact :

    A remote attacker could entice a user to process specially crafted input       in an application using yaml.load() from PyYAML, possibly resulting in       execution of arbitrary code with the privileges of the process or a       Denial of Service condition.
  Workaround :

    There is no known workaround at this time.

According to the version of the PyYAML package installed, the EulerOS Virtualization for ARM 64 installation on the remote host is affected by the following vulnerability :

  - In PyYAML before 4.1, the yaml.load() API could execute     arbitrary code. In other words, yaml.safe_load is not     used.(CVE-2017-18342)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the version of the PyYAML packages installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - 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.(CVE-2017-18342)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the version of the PyYAML package installed, the EulerOS Virtualization for ARM 64 installation on the remote host is affected by the following vulnerability :

  - In PyYAML before 4.1, the yaml.load() API could execute     arbitrary code. In other words, yaml.safe_load is not     used.i1/4^CVE-2017-18342i1/4%0

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update of the PyYAML package has been released.

New upstream release 5.1 (rhbz#1688414) Fixes CVE-2017-18342 (rhbz#1595744)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

pyyaml reports :

the PyYAML.load function could be easily exploited to call any Python function. That means it could call any system command using os.system()

According to the version of the PyYAML package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerability :

  - In PyYAML before 4.1, the yaml.load() API could execute     arbitrary code. In other words, yaml.safe_load is not     used.i1/4^CVE-2017-18342i1/4%0

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the version of the PyYAML package installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - In PyYAML before 4.1, the yaml.load() API could execute     arbitrary code. In other words, yaml.safe_load is not     used.(CVE-2017-18342)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
160271	Oracle Linux 8 : ol-automation-manager (ELSA-2022-9341)	Nessus	Oracle Linux Local Security Checks	critical
134731	GLSA-202003-45 : PyYAML: Arbitrary code execution	Nessus	Gentoo Local Security Checks	critical
132837	EulerOS Virtualization for ARM 64 3.0.5.0 : PyYAML (EulerOS-SA-2020-1083)	Nessus	Huawei Local Security Checks	critical
131365	EulerOS 2.0 SP8 : PyYAML (EulerOS-SA-2019-2299)	Nessus	Huawei Local Security Checks	critical
125567	EulerOS Virtualization for ARM 64 3.0.2.0 : PyYAML (EulerOS-SA-2019-1615)	Nessus	Huawei Local Security Checks	critical
125084	Photon OS 1.0: Pyyaml PHSA-2019-1.0-0224	Nessus	PhotonOS Local Security Checks	critical
124491	Fedora 30 : PyYAML (2019-44643e8bcb)	Nessus	Fedora Local Security Checks	critical
124287	FreeBSD : py-yaml -- arbitrary code execution (f6ea18bb-65b9-11e9-8b31-002590045d9c)	Nessus	FreeBSD Local Security Checks	critical
123910	EulerOS Virtualization 2.5.4 : PyYAML (EulerOS-SA-2019-1224)	Nessus	Huawei Local Security Checks	critical
123041	Fedora 28 : PyYAML (2019-779a9db46a)	Nessus	Fedora Local Security Checks	critical
122984	Fedora 29 : PyYAML (2019-bed9afe622)	Nessus	Fedora Local Security Checks	critical
122383	EulerOS 2.0 SP2 : PyYAML (EulerOS-SA-2019-1056)	Nessus	Huawei Local Security Checks	critical
122214	EulerOS 2.0 SP5 : PyYAML (EulerOS-SA-2019-1041)	Nessus	Huawei Local Security Checks	critical
122213	EulerOS 2.0 SP3 : PyYAML (EulerOS-SA-2019-1040)	Nessus	Huawei Local Security Checks	critical

Detections

Analytics

CVE-2017-18342

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical