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

    libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time     field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the
    *time fraction*, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not     (purposely) null terminated. This flaw most likely leads to a crash, but can also lead to heap contents     getting returned to the application when     [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used.(CVE-2024-7264)

Tenable has extracted the preceding description block directly from the EulerOS curl security advisory.

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

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

    libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing an ASN.1 Generalized Time     field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the
    *time fraction*, leading to a `strlen()` getting performed on a pointer to a heap buffer area that is not     (purposely) null terminated.This flaw most likely leads to a crash, but can also lead to heap contents     getting returned to the application when     [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used.(CVE-2024-7264)

    When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling,     to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead     wrongly consider the response as fine.  If the returned status reports another error than 'revoked' (like     for example 'unauthorized') it is not treated as a bad certficate.(CVE-2024-8096)

Tenable has extracted the preceding description block directly from the EulerOS curl security advisory.

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-758 advisory.

    Envoy is a cloud-native high-performance edge/middle/service proxy. A security vulnerability in Envoy     allows external clients to manipulate Envoy headers, potentially leading to unauthorized access or other     malicious actions within the mesh. This issue arises due to Envoy's default configuration of internal     trust boundaries, which considers all RFC1918 private address ranges as internal. The default behavior for     handling internal addresses in Envoy has been changed. Previously, RFC1918 IP addresses were automatically     considered internal, even if the internal_address_config was empty.  The default configuration of Envoy     will continue to trust internal addresses while in this release and it will not trust them by default in     next release. If you have tooling such as probes on your private network which need to be treated as     trusted (e.g. changing arbitrary x-envoy headers) please explicitly include those addresses or CIDR ranges     into `internal_address_config`. Successful exploitation could allow attackers to bypass security controls,     access sensitive data, or disrupt services within the mesh, like Istio. This issue has been addressed in     versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds     for this vulnerability. (CVE-2024-45806)

    Envoy is a cloud-native high-performance edge/middle/service proxy. A vulnerability has been identified in     Envoy that allows malicious attackers to inject unexpected content into access logs. This is achieved by     exploiting the lack of validation for the `REQUESTED_SERVER_NAME` field for access loggers. This issue has     been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no     known workarounds for this vulnerability. (CVE-2024-45808)

    Envoy is a cloud-native high-performance edge/middle/service proxy. Jwt filter will lead to an Envoy crash     when clear route cache with remote JWKs. In the following case: 1. remote JWKs are used, which requires     async header processing; 2. clear_route_cache is enabled on the provider; 3. header operations are enabled     in JWT filter, e.g. header to claims feature; 4. the routing table is configured in a way that the JWT     header operations modify requests to not match any route. When these conditions are met, a crash is     triggered in the upstream code due to nullptr reference conversion from route(). The root cause is the     ordering of continueDecoding and clearRouteCache. This issue has been addressed in versions 1.31.2,     1.30.6, and 1.29.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.
    (CVE-2024-45809)

    Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async     client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests     mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason     is http async client is duplicating the status code, another one is the destroy of router is called at the     destructor of the async stream, while the stream is deferred deleted at first. There will be problems that     the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment     fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request     mirrorring. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are     advised to upgrade. There are no known workarounds for this vulnerability. (CVE-2024-45810)

    libcurl's ASN1 parser code has the `GTime2str()` function, used for parsing anASN.1 Generalized Time     field. If given an syntactically incorrect field, theparser might end up using -1 for the length of the
    *time fraction*, leading toa `strlen()` getting performed on a pointer to a heap buffer area that is     not(purposely) null terminated.

    This flaw most likely leads to a crash, but can also lead to heap contentsgetting returned to the     application when[CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html) is used.
    (CVE-2024-7264)

Tenable has extracted the preceding description block directly from the tested product 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 NewStart CGSL host, running version MAIN 7.02, has curl packages installed that are affected by multiple vulnerabilities:

  - CVE-2023-38546 is a cookie injection vulnerability in the curl_easy_duphandle(), a function in libcurl     that duplicates easy handles.  When duplicating an easy handle, if cookies are enabled, the duplicated     easy handle will not duplicate the cookies themselves, but would instead set the filename to none.'     Therefore, when the duplicated easy handle is subsequently used, if a source was not set for the cookies,     libcurl would attempt to load them from the file named none' on the disk.  This vulnerability is rated     low, as the various conditions required for exploitation are unlikely.  (CVE-2023-38546)

  - This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the     specific series of conditions are met. libcurl performs transfers. In its API, an application creates     easy handles that are the individual handles for single transfers. libcurl provides a function call that     duplicates en easy handle called     [curl_easy_duphandle](https://curl.se/libcurl/c/curl_easy_duphandle.html). If a transfer has cookies     enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the     actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned     version of the handle would instead store the file name as `none` (using the four ASCII letters, no     quotes). Subsequent use of the cloned handle that does not explicitly set a source to load cookies from     would then inadvertently load cookies from a file named `none` - if such a file exists and is readable in     the current directory of the program using libcurl. And if using the correct file format of course.
    (CVE-2023-38546)

  - CVE-2023-38545 is a heap-based buffer overflow vulnerability in the SOCKS5 proxy handshake in libcurl and     curl.  When curl is given a hostname to pass along to a SOCKS5 proxy that is greater than 255 bytes in     length, it will switch to local name resolution in order to resolve the address before passing it on to     the SOCKS5 proxy. However, due to a bug introduced in 2020, this local name resolution could fail due to a     slow SOCKS5 handshake, causing curl to pass on the hostname greater than 255 bytes in length into the     target buffer, leading to a heap overflow.  The advisory for CVE-2023-38545 gives an example exploitation     scenario of a malicious HTTPS server redirecting to a specially crafted URL. While it might seem that an     attacker would need to influence the slowness of the SOCKS5 handshake, the advisory states that server     latency is likely slow enough to trigger this bug. (CVE-2023-38545)

  - This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to     pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting     done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected     to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due     to this bug, the local variable that means let the host resolve the name could get the wrong value     during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target     buffer instead of copying just the resolved address there. The target buffer being a heap based buffer,     and the host name coming from the URL that curl has been told to operate with. (CVE-2023-38545)

  - When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later     via the libcurl headers API. However, curl did not have a limit in how many or how large headers it would     accept in a response, allowing a malicious server to stream an endless series of headers and eventually     cause curl to run out of heap memory. (CVE-2023-38039)

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

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2025:1671 advisory.

    * openssl: SSL_select_next_proto buffer overread (CVE-2024-5535)
      * krb5: GSS message token handling (CVE-2024-37371)
      * curl: libcurl: ASN.1 date parser overread (CVE-2024-7264)
      * mysql: Thread Pooling unspecified vulnerability (CPU Oct 2024) (CVE-2024-21238)
      * mysql: X Plugin unspecified vulnerability (CPU Oct 2024) (CVE-2024-21196)
      * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21241)
      * mysql: Client programs unspecified vulnerability (CPU Oct 2024) (CVE-2024-21231)
      * mysql: Information Schema unspecified vulnerability (CPU Oct 2024) (CVE-2024-21197)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21218)
      * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21201)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21236)
      * mysql: Group Replication GCS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21237)
      * mysql: FTS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21203)
      * mysql: Health Monitor unspecified vulnerability (CPU Oct 2024) (CVE-2024-21212)
      * mysql: DML unspecified vulnerability (CPU Oct 2024) (CVE-2024-21219)
      * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21230)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21213)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21194)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21199)
      * mysql: PS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21193)
      * mysql: DDL unspecified vulnerability (CPU Oct 2024) (CVE-2024-21198)
      * mysql: mysqldump unspecified vulnerability (CPU Oct 2024) (CVE-2024-21247)
      * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21239)
      * curl: curl netrc password leak (CVE-2024-11053)
      * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21497)
      * mysql: MySQL Server Options Vulnerability (CVE-2025-21520)
      * mysql: High Privilege Denial of Service Vulnerability in MySQL Server (CVE-2025-21490)
      * mysql: Information Schema unspecified vulnerability (CPU Jan 2025) (CVE-2025-21529)
      * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21531)
      * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21504)
      * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21540)
      * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21555)
      * mysql: Packaging unspecified vulnerability (CPU Jan 2025) (CVE-2025-21543)
      * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21491)
      * mysql: DDL unspecified vulnerability (CPU Jan 2025) (CVE-2025-21525)
      * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21536)
      * mysql: Thread Pooling unspecified vulnerability (CPU Jan 2025) (CVE-2025-21521)
      * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21501)
      * mysql: Performance Schema unspecified vulnerability (CPU Jan 2025) (CVE-2025-21534)
      * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21494)
      * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21519)
      * mysql: Parser unspecified vulnerability (CPU Jan 2025) (CVE-2025-21522)
      * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21503)
      * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21518)
      * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21559)
      * mysql: Privilege Misuse in MySQL Server Security Component (CVE-2025-21546)
      * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21500)
      * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21523)
      * mysql: Components Services unspecified vulnerability (CPU Jan 2025) (CVE-2025-21505)

Tenable has extracted the preceding description block directly from the AlmaLinux 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 RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2025:1671 advisory.

    * openssl: SSL_select_next_proto buffer overread (CVE-2024-5535)

    * krb5: GSS message token handling (CVE-2024-37371)

    * curl: libcurl: ASN.1 date parser overread (CVE-2024-7264)

    * mysql: Thread Pooling unspecified vulnerability (CPU Oct 2024) (CVE-2024-21238)

    * mysql: X Plugin unspecified vulnerability (CPU Oct 2024) (CVE-2024-21196)

    * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21241)

    * mysql: Client programs unspecified vulnerability (CPU Oct 2024) (CVE-2024-21231)

    * mysql: Information Schema unspecified vulnerability (CPU Oct 2024) (CVE-2024-21197)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21218)

    * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21201)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21236)

    * mysql: Group Replication GCS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21237)

    * mysql: FTS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21203)

    * mysql: Health Monitor unspecified vulnerability (CPU Oct 2024) (CVE-2024-21212)

    * mysql: DML unspecified vulnerability (CPU Oct 2024) (CVE-2024-21219)

    * mysql: Optimizer unspecified vulnerability (CPU Oct 2024) (CVE-2024-21230)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21213)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21194)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21199)

    * mysql: PS unspecified vulnerability (CPU Oct 2024) (CVE-2024-21193)

    * mysql: DDL unspecified vulnerability (CPU Oct 2024) (CVE-2024-21198)

    * mysql: mysqldump unspecified vulnerability (CPU Oct 2024) (CVE-2024-21247)

    * mysql: InnoDB unspecified vulnerability (CPU Oct 2024) (CVE-2024-21239)

    * curl: curl netrc password leak (CVE-2024-11053)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21497)

    * mysql: MySQL Server Options Vulnerability (CVE-2025-21520)

    * mysql: High Privilege Denial of Service Vulnerability in MySQL Server (CVE-2025-21490)

    * mysql: Information Schema unspecified vulnerability (CPU Jan 2025) (CVE-2025-21529)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21531)

    * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21504)

    * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21540)

    * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21555)

    * mysql: Packaging unspecified vulnerability (CPU Jan 2025) (CVE-2025-21543)

    * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21491)

    * mysql: DDL unspecified vulnerability (CPU Jan 2025) (CVE-2025-21525)

    * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21536)

    * mysql: Thread Pooling unspecified vulnerability (CPU Jan 2025) (CVE-2025-21521)

    * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21501)

    * mysql: Performance Schema unspecified vulnerability (CPU Jan 2025) (CVE-2025-21534)

    * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21494)

    * mysql: Privileges unspecified vulnerability (CPU Jan 2025) (CVE-2025-21519)

    * mysql: Parser unspecified vulnerability (CPU Jan 2025) (CVE-2025-21522)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21503)

    * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21518)

    * mysql: MySQL Server InnoDB Denial of Service and Unauthorized Data Modification Vulnerability     (CVE-2025-21559)

    * mysql: Privilege Misuse in MySQL Server Security Component (CVE-2025-21546)

    * mysql: Optimizer unspecified vulnerability (CPU Jan 2025) (CVE-2025-21500)

    * mysql: InnoDB unspecified vulnerability (CPU Jan 2025) (CVE-2025-21523)

    * mysql: Components Services unspecified vulnerability (CPU Jan 2025) (CVE-2025-21505)

Tenable has extracted the preceding description block directly from the RockyLinux 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 version of Splunk installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the SVD-2024-0303 advisory.

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
210234	EulerOS 2.0 SP12 : curl (EulerOS-SA-2024-2795)	Nessus	Huawei Local Security Checks	2024/11/4	2024/11/4	medium
210676	EulerOS 2.0 SP9 : curl (EulerOS-SA-2024-2809)	Nessus	Huawei Local Security Checks	2024/11/8	2024/11/8	medium
211373	Amazon Linux 2023 : ecs-service-connect-agent (ALAS2023-2024-758)	Nessus	Amazon Linux Local Security Checks	2024/11/14	2024/11/15	medium
242816	NewStart CGSL MAIN 7.02 : curl Multiple Vulnerabilities (NS-SA-2025-0111)	Nessus	NewStart CGSL Local Security Checks	2025/7/25	2025/7/26	critical
216621	AlmaLinux 9 : mysql (ALSA-2025:1671)	Nessus	Alma Linux Local Security Checks	2025/2/21	2025/4/18	critical
232906	RockyLinux 9 : mysql (RLSA-2025:1671)	Nessus	Rocky Linux Local Security Checks	2025/3/19	2025/4/18	critical
235985	Alibaba Cloud Linux 3 : 0038: mysql:8.0 (ALINUX3-SA-2025:0038)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/14	critical
194923	Splunk Enterprise 9.0.0 < 9.0.9, 9.1.0 < 9.1.4, 9.2.0 < 9.2.1 (SVD-2024-0303)	Nessus	CGI abuses	2024/5/2	2025/5/12	critical

检测

插件搜索

medium

medium

medium

critical

critical

critical

critical

critical