リモートのUbuntu 16.04LTS/18.04 LTS/20.04 LTS/20.10ホストには、USN-4665-1のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。Nessus はこの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ頼っていることに注意してください。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  -ダングリングポインターの使用により、libcurl 7.29.0 〜 7.71.1 は、データ送信時に誤った接続を使用する可能性があります。(CVE-2020-8231)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The remote NewStart CGSL host, running version MAIN 6.02, has curl packages installed that are affected by multiple vulnerabilities:

  - Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending     data. (CVE-2020-8231)

  - A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to     a given IP address and port, and this way potentially make curl extract information about services that     are otherwise private and not disclosed, for example doing port scanning and service banner extractions.
    (CVE-2020-8284)

  - curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue     in FTP wildcard match parsing. (CVE-2020-8285)

  - curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to     insufficient verification of the OCSP response. (CVE-2020-8286)

  - When curl is instructed to download content using the metalink feature, thecontents is verified against a     hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same     contentfrom a set of different URLs, potentially hosted by different servers and theclient can then     download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting     the contents has been breached and the contentsof the specific file on that server is replaced with a     modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload.
    It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and     instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the     file ondisk. (CVE-2021-22922)

  - When curl is instructed to get content using the metalink feature, and a user name and password are used     to download the metalink XML file, those same credentials are then subsequently passed on to each of the     servers from which curl will download or try to download the contents from. Often contrary to the user's     expectations and intentions and without telling the user it happened. (CVE-2021-22923)

  - libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of     them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert'     into account and it compared the involved paths *case insensitively*,which could lead to libcurl reusing     wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary     depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can     setto qualify how to verify the server certificate. (CVE-2021-22924)

  - A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an     IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL`     or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly     crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations
    **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear     text over the network. (CVE-2021-22946)

  - When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to     upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches.
    curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using     and trustingthe responses it got *before* the TLS handshake as if they were authenticated.Using this flaw,     it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS     traffic from the legitimate server and trick curl into sending data back to the user thinking the     attacker's injected data comes from the TLS-protected server. (CVE-2021-22947)

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

According to the versions of the curl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - Vulnerability Summary for CVE-2020-8169(CVE-2020-8169)

  - Vulnerability Summary for CVE-2020-8177(CVE-2020-8177)

  - Expired pointer dereference via multi API with     `CURLOPT_CONNECT_ONLY` option set(CVE-2020-8231)

  - curl 7.21.0 to and including 7.73.0 is vulnerable to     uncontrolled recursion due to a stack overflow issue in     FTP wildcard match parsing.(CVE-2020-8285)

  - curl 7.41.0 through 7.73.0 is vulnerable to an improper     check for certificate revocation due to insufficient     verification of the OCSP response.(CVE-2020-8286)

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.

The remote SUSE Linux SLES11 host has packages installed that are affected by a vulnerability as referenced in the SUSE- SU-2020:14481-1 advisory.

  - Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending     data. (CVE-2020-8231)

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

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

    The curl packages provide the libcurl library and the curl utility for downloading files from servers     using various protocols, including HTTP, FTP, and LDAP.

    Security Fix(es):

    * curl: FTP PASV command response can cause curl to connect to arbitrary host (CVE-2020-8284)

    * curl: Malicious FTP server can trigger stack overflow when CURLOPT_CHUNK_BGN_FUNCTION is used     (CVE-2020-8285)

    * curl: Inferior OCSP verification (CVE-2020-8286)

    * curl: Expired pointer dereference via multi API with CURLOPT_CONNECT_ONLY option set (CVE-2020-8231)

    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.4 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-2021-1610 advisory.

    - curl: Inferior OCSP verification (CVE-2020-8286)
    - libcurl: FTP wildcard stack overflow (CVE-2020-8285)
    - curl: trusting FTP PASV responses (CVE-2020-8284)

Tenable has extracted the preceding description block directly from the Oracle 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.

curl security problems :

CVE-2020-8231: wrong connect-only connection

An application that performs multiple requests with libcurl's multi API and sets the CURLOPT_CONNECT_ONLY option, might in rare circumstances experience that when subsequently using the setup connect-only transfer, libcurl will pick and use the wrong connection
- and instead pick another one the application has created since then.

CURLOPT_CONNECT_ONLY is the option to tell libcurl to not perform an actual transfer, only connect. When that operation is completed, libcurl remembers which connection it used for that transfer and 'easy handle'. It remembers the connection using a pointer to the internal connectdata struct in memory.

If more transfers are then done with the same multi handle before the connect-only connection is used, leading to the initial connect-only connection to get closed (for example due to idle time-out) while also new transfers (and connections) are setup, such a new connection might end up getting the exact same memory address as the now closed connect-only connection.

If after those operations, the application then wants to use the original transfer's connect-only setup to for example use curl_easy_send() to send raw data over that connection, libcurl could erroneously find an existing connection still being alive at the address it remembered since before even though this is now a new and different connection.

The application could then accidentally send data over that connection which wasn't at all intended for that recipient, entirely unknowingly.

- fix expired pointer dereference via multi API with     `CURLOPT_CONNECT_ONLY` option set (CVE-2020-8231)

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.

This update for curl fixes the following issues :

  - An application that performs multiple requests with     libcurl's multi API and sets the 'CURLOPT_CONNECT_ONLY'     option, might in rare circumstances experience that when     subsequently using the setup connect-only transfer,     libcurl will pick and use the wrong connection and     instead pick another one the application has created     since then. [bsc#1175109, CVE-2020-8231]

This update was imported from the SUSE:SLE-15:Update update project.

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

  - curl: Expired pointer dereference via multi API with CURLOPT_CONNECT_ONLY option set (CVE-2020-8231)

  - curl: FTP PASV command response can cause curl to connect to arbitrary host (CVE-2020-8284)

  - curl: Malicious FTP server can trigger stack overflow when CURLOPT_CHUNK_BGN_FUNCTION is used     (CVE-2020-8285)

  - curl: Inferior OCSP verification (CVE-2020-8286)

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

The remote AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2021:1610 advisory.

  - Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending     data. (CVE-2020-8231)

  - A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to     a given IP address and port, and this way potentially make curl extract information about services that     are otherwise private and not disclosed, for example doing port scanning and service banner extractions.
    (CVE-2020-8284)

  - curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue     in FTP wildcard match parsing. (CVE-2020-8285)

  - curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to     insufficient verification of the OCSP response. (CVE-2020-8286)

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

The remote Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-4665-1 advisory.

    Marc Aldorasi discovered that curl incorrectly handled the libcurl CURLOPT_CONNECT_ONLY option. This could     result in data being sent to the wrong destination, possibly exposing sensitive information. This issue     only affected Ubuntu 20.10. (CVE-2020-8231)

    Varnavas Papaioannou discovered that curl incorrectly handled FTP PASV responses. An attacker could     possibly use this issue to trick curl into connecting to an arbitrary IP address and be used to perform     port scanner and other information gathering. (CVE-2020-8284)

    It was discovered that curl incorrectly handled FTP wildcard matchins. A remote attacker could possibly     use this issue to cause curl to consume resources and crash, resulting in a denial of service.
    (CVE-2020-8285)

    It was discovered that curl incorrectly handled OCSP response verification. A remote attacker could     possibly use this issue to provide a fraudulent OCSP response. (CVE-2020-8286)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending     data. (CVE-2020-8231)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
144011	Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS : curl の脆弱性 (USN-4665-1)	Nessus	Ubuntu Local Security Checks	2020/12/9	2025/9/3	high
194927	Universal Forwarders < 8.1.14、8.2.0 < 8.2.11、9.0.0 < 9.0.5 (SVD-2023-0614)	Nessus	CGI abuses	2024/5/2	2024/5/30	critical
260306	Linux Distros のパッチ未適用の脆弱性: CVE-2020-8231	Nessus	Misc.	2025/9/2	2025/9/4	high
167463	NewStart CGSL MAIN 6.02 : curl Multiple Vulnerabilities (NS-SA-2022-0083)	Nessus	NewStart CGSL Local Security Checks	2022/11/15	2023/10/4	high
147470	EulerOS Virtualization 2.9.1 : curl (EulerOS-SA-2021-1596)	Nessus	Huawei Local Security Checks	2021/3/10	2024/1/11	high
150677	SUSE SLES11 Security Update : curl (SUSE-SU-2020:14481-1)	Nessus	SuSE Local Security Checks	2021/6/10	2023/12/13	high
149676	RHEL 8 : curl (RHSA-2021:1610)	Nessus	Red Hat Local Security Checks	2021/5/19	2025/3/6	high
149932	Oracle Linux 8 : curl (ELSA-2021-1610)	Nessus	Oracle Linux Local Security Checks	2021/5/26	2024/10/22	high
139715	FreeBSD : curl -- expired pointer dereference vulnerability (b905dff4-e227-11ea-b0ea-08002728f74c)	Nessus	FreeBSD Local Security Checks	2020/8/20	2024/2/23	high
139737	Fedora 32 : curl (2020-da832cb434)	Nessus	Fedora Local Security Checks	2020/8/21	2024/2/23	high
140368	openSUSE Security Update : curl (openSUSE-2020-1345)	Nessus	SuSE Local Security Checks	2020/9/8	2024/2/21	high
149767	CentOS 8 : curl (CESA-2021:1610)	Nessus	CentOS Local Security Checks	2021/5/19	2023/9/12	high
157525	AlmaLinux 8 : curl (ALSA-2021:1610)	Nessus	Alma Linux Local Security Checks	2022/2/9	2023/11/13	high
194927	Universal Forwarders < 8.1.14, 8.2.0 < 8.2.11, 9.0.0 < 9.0.5 (SVD-2023-0614)	Nessus	CGI abuses	2024/5/2	2024/5/30	critical
144011	Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS : curl vulnerabilities (USN-4665-1)	Nessus	Ubuntu Local Security Checks	2020/12/9	2025/9/3	high
260306	Linux Distros Unpatched Vulnerability : CVE-2020-8231	Nessus	Misc.	2025/9/2	2025/9/4	high

检测

插件搜索

high

critical

high

high

high

high

high

high

high

high

high

high

high

critical

high

high