The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2021:0037 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2020-11023:
    In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing option     elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods     (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
    A flaw was found in jQuery. HTML containing option elements from untrusted sources are passed, even after     sanitizing, to one of jQuery's DOM manipulation methods, which may execute untrusted code. The highest     threat from this vulnerability is to data confidentiality and integrity.

    CVE-2020-15720:
    In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests     certificate validation. Since the verify parameter was hard-coded in all request functions, it was not     possible to override the setting. As a result, tools making use of this class, such as the pki-server     command, may have been vulnerable to Person-in-the-Middle attacks in certain non-localhost use cases. This     is fixed in 10.9.0-b1. A flaw was found in PKI, where the dogtag's pki.client.PKIConnection class disables     the python-requests certificate validation. This flaw allows an attacker to intercept a connection between     a FreeIPA client and a server, and execute an active Man-in-the-Middle attack. The highest threat from     this vulnerability is to confidentiality and integrity.

    CVE-2020-1935:
    In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used     an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led     to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly     handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered     unlikely. A flaw was found in Apache Tomcat. The HTTP header parsing code used an approach to end-of-line     (EOL) parsing that allowed some invalid HTTP headers to be parsed as valid. This led to the possibility of     HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid     Transfer-Encoding header in a particular manner. The highest threat with this vulnerability is system     availability.

    CVE-2020-1938:
    When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to     Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP     connection. If such connections are available to an attacker, they can be exploited in ways that may be     surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped     with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected     (and recommended in the security guide) that this Connector would be disabled if not required. This     vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the     web application - processing any file in the web application as a JSP Further, if the web application     allowed file upload and stored those files within the web application (or the attacker was able to control     the content of the web application by some other means) then this, along with the ability to process a     file as a JSP, made remote code execution possible. It is important to note that mitigation is only     required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth     approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to     Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP     Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading     to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.
    CVE-2020-1938 is a file read/inclusion vulnerability in the AJP connector in Apache Tomcat. This is     enabled by default with a default configuration port of 8009. A remote, unauthenticated attacker could     exploit this vulnerability to read web application files from a vulnerable server. In instances where the     vulnerable server allows file uploads, an attacker could upload malicious JavaServer Pages (JSP) code     within a variety of file types and trigger this vulnerability to gain remote code execution (RCE).

    CVE-2022-25762     If a web application sends a WebSocket message concurrently with the WebSocket connection closing when     running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the     application will continue to use the socket after it has been closed. The error handling triggered in this     case could cause the a pooled object to be placed in the pool twice. This could result in subsequent     connections using the same object concurrently which could result in data being returned to the wrong use     and/or other errors.

    CVE-2021-3551:
    ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when     announcing a new security problem. When the candidate has been publicized, the details for this candidate     will be provided.

Tenable has extracted the preceding description block directly from the Alibaba Cloud Linux security advisory.

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

The remote CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2020:4847 advisory.

  - jquery: Cross-site scripting via cross-domain ajax requests (CVE-2015-9251)

  - bootstrap: XSS in the data-target attribute (CVE-2016-10735)

  - bootstrap: Cross-site Scripting (XSS) in the collapse data-parent attribute (CVE-2018-14040)

  - bootstrap: Cross-site Scripting (XSS) in the data-container property of tooltip (CVE-2018-14042)

  - pki-core: Reflected XSS in 'path length' constraint field in CA's Agent page (CVE-2019-10146)

  - pki-core/pki-kra: Reflected XSS in recoveryID search field at KRA's DRM agent page in authorize recovery     tab (CVE-2019-10179)

  - pki-core: Reflected XSS in getcookies?url= endpoint in CA (CVE-2019-10221)

  - jquery: Prototype pollution in object's prototype leading to denial of service, remote code execution, or     property injection (CVE-2019-11358)

  - bootstrap: XSS in the tooltip or popover data-template attribute (CVE-2019-8331)

  - jquery: Cross-site scripting due to improper injQuery.htmlPrefilter method (CVE-2020-11022)

  - jquery: Untrusted code execution via <option> tag in HTML passed to DOM manipulation methods     (CVE-2020-11023)

  - pki: Dogtag's python client does not validate certificates (CVE-2020-15720)

  - pki-core: KRA vulnerable to reflected XSS via the getPk12 page (CVE-2020-1721)

  - tomcat: Mishandling of Transfer-Encoding header allows for HTTP request smuggling (CVE-2020-1935)

  - tomcat: Apache Tomcat AJP File Read/Inclusion Vulnerability (CVE-2020-1938)

  - pki-core: XSS in the certificate search results (CVE-2020-25715)

  - tomcat: request mixup (CVE-2022-25762)

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests     certificate validation. Since the verify parameter was hard-coded in all request functions, it was not     possible to override the setting. As a result, tools making use of this class, such as the pki-server     command, may have been vulnerable to Person-in-the-Middle attacks in certain non-localhost use cases. This     is fixed in 10.9.0-b1. (CVE-2020-15720)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:4847 advisory.

    The Public Key Infrastructure (PKI) Core contains fundamental packages required by Red Hat Certificate     System.

    Security Fix(es):

    * jquery: Cross-site scripting via cross-domain ajax requests (CVE-2015-9251)

    * bootstrap: XSS in the data-target attribute (CVE-2016-10735)

    * bootstrap: Cross-site Scripting (XSS) in the collapse data-parent attribute (CVE-2018-14040)

    * bootstrap: Cross-site Scripting (XSS) in the data-container property of tooltip (CVE-2018-14042)

    * bootstrap: XSS in the tooltip or popover data-template attribute (CVE-2019-8331)

    * jquery: Prototype pollution in object's prototype leading to denial of service, remote code execution,     or property injection (CVE-2019-11358)

    * jquery: Cross-site scripting due to improper injQuery.htmlPrefilter method (CVE-2020-11022)

    * jquery: Passing HTML containing <option> elements to manipulation methods could result in untrusted code     execution (CVE-2020-11023)

    * pki: Dogtag's python client does not validate certificates (CVE-2020-15720)

    * pki-core: Reflected XSS in 'path length' constraint field in CA's Agent page (CVE-2019-10146)

    * pki-core/pki-kra: Reflected XSS in recoveryID search field at KRA's DRM agent page in authorize recovery     tab (CVE-2019-10179)

    * pki-core: Reflected XSS in getcookies?url= endpoint in CA (CVE-2019-10221)

    * pki-core: KRA vulnerable to reflected XSS via the getPk12 page (CVE-2020-1721)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.3 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

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

  - In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. (CVE-2018-14040)

  - In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. (CVE-2018-14042)

  - jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request     is performed without the dataType option, causing text/javascript responses to be executed.
    (CVE-2015-9251)

  - In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target     attribute, a different vulnerability than CVE-2018-14041. (CVE-2016-10735)

  - In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template     attribute. (CVE-2019-8331)

  - In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources -     even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and     others) may execute untrusted code. This problem is patched in jQuery 3.5.0. (CVE-2020-11022)

  - jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true,     {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable
    __proto__ property, it could extend the native Object.prototype. (CVE-2019-11358)

  - A Reflected Cross Site Scripting flaw was found in all pki-core 10.x.x versions module from the pki-core     server due to the CA Agent Service not properly sanitizing the certificate request page. An attacker could     inject a specially crafted value that will be executed on the victim's browser. (CVE-2019-10146)

  - A vulnerability was found in all pki-core 10.x.x versions, where the Key Recovery Authority (KRA) Agent     Service did not properly sanitize recovery request search page, enabling a Reflected Cross Site Scripting     (XSS) vulnerability. An attacker could trick an authenticated victim into executing specially crafted     Javascript code. (CVE-2019-10179)

  - A Reflected Cross Site Scripting vulnerability was found in all pki-core 10.x.x versions, where the pki-ca     module from the pki-core server. This flaw is caused by missing sanitization of the GET URL parameters. An     attacker could abuse this flaw to trick an authenticated user into clicking a specially crafted link which     can execute arbitrary code when viewed in a browser. (CVE-2019-10221)

  - A flaw was found in the Key Recovery Authority (KRA) Agent Service in pki-core 10.10.5 where it did not     properly sanitize the recovery ID during a key recovery request, enabling a reflected cross-site scripting     (XSS) vulnerability. An attacker could trick an authenticated victim into executing specially crafted     Javascript code. (CVE-2020-1721)

  - In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option>     elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods     (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
    (CVE-2020-11023)

  - In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests     certificate validation. Since the verify parameter was hard-coded in all request functions, it was not     possible to override the setting. As a result, tools making use of this class, such as the pki-server     command, may have been vulnerable to Person-in-the-Middle attacks in certain non-localhost use cases. This     is fixed in 10.9.0-b1. (CVE-2020-15720)

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

ID	Name	Product	Family	Published	Updated	Severity
236419	Alibaba Cloud Linux 3 : 0037: pki-core:10.6 (ALINUX3-SA-2021:0037)	Nessus	Alibaba Cloud Linux Local Security Checks	5/14/2025	10/1/2025	critical
145989	CentOS 8 : pki-core:10.6 and pki-deps:10.6 (CESA-2020:4847)	Nessus	CentOS Local Security Checks	2/1/2021	1/24/2025	medium
223435	Linux Distros Unpatched Vulnerability : CVE-2020-15720	Nessus	Misc.	3/4/2025	9/15/2025	medium
142409	RHEL 8 : pki-core:10.6 and pki-deps:10.6 (RHSA-2020:4847)	Nessus	Red Hat Local Security Checks	11/4/2020	10/1/2025	critical
180899	Oracle Linux 8 : pki-core:10.6 / and / pki-deps:10.6 (ELSA-2020-4847)	Nessus	Oracle Linux Local Security Checks	9/7/2023	1/24/2025	medium

Detections

Analytics

Plugins Search

critical

medium

medium

critical

medium