According to its self-reported version, the Tenable Security Center running on the remote host is version 6.3.0, 6.4.0, 6.4.5, or 6.5.1. It is, therefore, affected by multiple vulnerabilities as referenced in the TNS-2025-04 advisory.

  - When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache     entry, making it end sooner or later than otherwise intended. This affects curl using applications that     enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like     `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS     cache either needs to have been populated manually or there needs to have been previous HTTPS accesses     done as the cache needs to have entries for the domains involved to trigger this problem.) When     `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's     expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The     result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different     period of time than what was asked for by the origin server. If `example.com` for example stops supporting     HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set)     timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently     switch back to insecure HTTP earlier than otherwise intended. (CVE-2024-9681)

  - Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial     can lead to out-of-bounds memory reads or writes. (CVE-2024-9143)

  - Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only named curves are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any     problematic use-cases would have to be using an exotic curve encoding. The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with exotic explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot     easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
    (CVE-2024-9143)

  - When asked to both use a `.netrc` file for credentials and to follow HTTP redirects, curl could leak the     password used for the first host to the followed-to host under certain circumstances. This flaw only     manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry     either omits just the password or omits both login and password. (CVE-2024-11053)

  - Issue summary: A timing side-channel which could potentially allow recovering the private key exists in     the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations     could allow recovering the private key by an attacker. However, measuring the timing would require either     local access to the signing application or a very fast network connection with low latency. There is a     timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This     can happen with significant probability only for some of the supported elliptic curves. In particular the     NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located     in the same physical computer or must have a very fast network connection with low latency. For that     reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are     affected by this issue. (CVE-2024-13176)

  - libcurl's ASN1 parser has this utf8asn1str() function used for parsing an ASN.1 UTF-8 string. Itcan detect     an invalid field and return error. Unfortunately, when doing so it also invokes `free()` on a 4 byte     localstack buffer. Most modern malloc implementations detect this error and immediately abort. Some     however accept the input pointer and add that memory to its list of available chunks. This leads to the     overwriting of nearby stack memory. The content of the overwrite is decided by the `free()`     implementation; likely to be memory pointers and a set of flags. The most likely outcome of exploting this     flaw is a crash, although it cannot be ruled out that more serious results can be had in special     circumstances. (CVE-2024-6197)

  - libcurl's URL API function [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) offers punycode     conversions, to and from IDN. Asking to convert a name that is exactly 256 bytes, libcurl ends up reading     outside of a stack based buffer when built to use the *macidn* IDN backend. The conversion function then     fills up the provided buffer exactly - but does not null terminate the string. This flaw can lead to stack     contents accidently getting returned as part of the converted string. (CVE-2024-6874)

  - 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)

  - When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the     password used for the first host to the followed-to host under certain circumstances. This flaw only     manifests itself if the netrc file has a `default` entry that omits both login and password. A rare     circumstance. (CVE-2025-0167)

  - libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel     after having completed a threaded name resolve. (CVE-2025-0665)

  - When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the     `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow     would make libcurl perform a buffer overflow. (CVE-2025-0725)

  - In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before     8.4.5, when http request module parses HTTP response obtained from a server, folded headers are parsed     incorrectly, which may lead to misinterpreting the response and using incorrect headers, MIME types, etc.
    (CVE-2025-1217)

  - In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before     8.4.5, when requesting a HTTP resource using the DOM or SimpleXML extensions, the wrong content-type     header is used to determine the charset when the requested resource performs a redirect. This may cause     the resulting document to be parsed incorrectly or bypass validations. (CVE-2025-1219)

  - In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before     8.4.5, when receiving headers from HTTP server, the headers missing a colon (:) are treated as valid     headers even though they are not. This may confuse applications into accepting invalid headers.
    (CVE-2025-1734)

  - In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before     8.4.5, when user-supplied headers are sent, the insufficient validation of the end-of-line characters may     prevent certain headers from being sent or lead to certain headers be misinterpreted. (CVE-2025-1736)

  - In PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before     8.4.5, when parsing HTTP redirect in the response to an HTTP request, there is currently limit on the     location value size caused by limited size of the location buffer to 1024. However as per RFC9110, the     limit is recommended to be 8000. This may lead to incorrect URL truncation and redirecting to a wrong     location. (CVE-2025-1861)

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-2026-1603 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 versions of Oracle Database Server installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2024 CPU advisory.

  - Vulnerability in the Oracle Spatial and Graph (libcurl2) component of Oracle Database Server. Supported     versions that are affected are 19.3-19.24, 21.3-21.15 and 23.4-23.5. Difficult to exploit vulnerability     allows unauthenticated attacker with network access via HTTP to compromise Oracle Spatial and Graph     (libcurl2). Successful attacks require human interaction from a person other than the attacker. Successful     attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable     crash (complete DOS) of Oracle Spatial and Graph (libcurl2). (CVE-2024-7264)

  - Vulnerability in the Oracle Database Security (OpenSSL) component of Oracle Database Server. Supported     versions that are affected are 23.4-23.5. Easily exploitable vulnerability allows unauthenticated attacker     with network access via multiple protocols to compromise Oracle Database Security (OpenSSL). Successful     attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service     (partial DOS) of Oracle Database Security (OpenSSL). (CVE-2024-5535, CVE-2024-6119)

  - Vulnerability in the Fleet Patching and Provisioning - Micronaut (Netty) component of Oracle Database     Server. Supported versions that are affected are 23.4-23.5. Easily exploitable vulnerability allows low     privileged attacker having Authenticated User privilege with network access via HTTP to compromise Fleet     Patching and Provisioning - Micronaut (Netty). Successful attacks of this vulnerability can result in     unauthorized ability to cause a partial denial of service (partial DOS) of Fleet Patching and Provisioning
    - Micronaut (Netty). (CVE-2024-29025)

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 installation on the remote host is affected by the following vulnerabilities :

    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)

    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 these issues 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-2025:1673 advisory.

    MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld)     and many client programs and libraries.

    Security Fix(es):

    * 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)

    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.

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 host is running a version of macOS / Mac OS X that is 15.x prior to 15.7.3. It is, therefore, affected by multiple vulnerabilities:

  - A vulnerability has been identified in the libarchive library. This flaw can be triggered when file     streams are piped into bsdtar, potentially allowing for reading past the end of the file. This out-of-     bounds read can lead to unintended consequences, including unpredictable program behavior, memory     corruption, or a denial-of-service condition. (CVE-2025-5918)

  - 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)

  - The issue was addressed by adding additional logic. This issue is fixed in macOS Sequoia 15.7.3. An app     may be able to bypass launch constraint protections and execute malicious code with elevated privileges.
    (CVE-2025-43320)

  - A logic issue was addressed with improved restrictions. This issue is fixed in macOS Sonoma 14.8.3, macOS     Sequoia 15.7.3. An app may be able to access protected user data. (CVE-2025-43416)

  - A parsing issue in the handling of directory paths was addressed with improved path validation. This issue     is fixed in macOS Sonoma 14.8.3, macOS Tahoe 26.1, macOS Sequoia 15.7.3. An app may be able to access     sensitive user data. (CVE-2025-43463)

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

ID	Name	Product	Family	Published	Updated	Severity
234507	Tenable Security Center Multiple Vulnerabilities (TNS-2025-04)	Nessus	Misc.	4/16/2025	4/16/2025	high
311314	Amazon Linux 2023 : ecs-service-connect-agent (ALAS2023-2026-1603)	Nessus	Amazon Linux Local Security Checks	4/30/2026	5/2/2026	medium
209306	Oracle Database Server (October 2024 CPU)	Nessus	Databases	10/18/2024	1/24/2025	medium
210657	EulerOS 2.0 SP10 : curl (EulerOS-SA-2024-2901)	Nessus	Huawei Local Security Checks	11/8/2024	11/8/2024	medium
216487	RHEL 8 : mysql:8.0 (RHSA-2025:1673)	Nessus	Red Hat Local Security Checks	2/19/2025	6/5/2025	critical
278571	macOS 15.x < 15.7.3 Multiple Vulnerabilities (125887)	Nessus	MacOS X Local Security Checks	12/12/2025	2/24/2026	high

Detections

Analytics

Plugins Search

high

medium

medium

medium

critical

high