根据其自我报告的版本，远程主机上运行的 Tenable Security Center 版本为 6.3.0、6.4.0、6.4.5 或 6.5.1。因此，该软件受到 TNS-2025-04 公告中提及的多个漏洞影响。

  - 如果 curl 必须使用 HSTS，子域的到期时间可能会覆盖父域的缓存条目，导致其到期时间较预期提早或延迟。这会影响使用启用 HSTS 的应用程序，并且这些应用程序使用具有不安全 `HTTP://` 方案的 URL，并针对 `x.example.com` 和 `example.com` 之类的主机执行传输，其中第一个主机是第二个主机的子域。（HSTS 缓存要么需要手动填充，要么需要之前有过 HTTPS 访问，因为缓存中必须包含相关域名的条目才能触发此问题。）当 `x.example.com` 返回 `Strict-Transport-Security:` 标头时，此漏洞可能会导致子域名的过期超时时间*溢出*，并在 curl 的 HSTS 缓存中被错误地设置为父域名 `example.com` 的值。触发此错误的结果就是导致对 `example.com` 的 HTTP 访问转换为 HTTPS 访问，并且访问时段与源服务器所请求的时段不同。例如，如果 `example.com` 在到期时间后停止支持 HTTPS，则 curl 可能无法访问 `http://example.com`，直到（错误设置的）超时时间过期。此错误还有可能导致父项*提早*到期，从而造成 curl 无意中比预期更早切换回不安全的 HTTP。(CVE-2024-9681)

  - 使用字段多项式具有不受信任的显式值的低级 GF(2^m) 椭圆曲线 API 可导致越界内存读取或写入。(CVE-2024-9143)

  - 问题摘要：使用字段多项式具有不受信任的显式值的低级 GF(2^m) 椭圆曲线 API 可导致越界内存读取或写入。影响摘要：越界内存写入可导致应用程序崩溃，甚至可能导致远程代码执行，但是，在我们所知的涉及椭圆曲线加密的所有协议中，要么仅支持指定的曲线，要么如果支持显式曲线参数，则其针对无法表示有问题的输入值的二进制 (GF(2^m)) 曲线指定 X9.62 编码。因此，存在易受攻击的应用程序的可能性很低。特别是，X9.62 编码用于 X.509 证书中的 ECC 密钥，因此处理 X.509 证书的上下文中不会发生有问题的输入。任何有问题的用例必须使用异常曲线编码。受影响的 API 包括：
    EC_GROUP_new_curve_GF2m()、EC_GROUP_new_from_params() 和多个支持性 BN_GF2m_*() 函数。
    使用异常显式二进制 (GF(2^m)) 曲线参数的应用程序（通过上述 API 或类似 API 可以用零常数项表示无效的域多项式）可能会因外部读取或写入而突然终止数组边界。无法轻易排除执行远程代码的可能性。3.3、3.2、3.1 和 3.0 中的 FIPS 模块不受此问题影响。
    (CVE-2024-9143)

  - 当要求使用 `.netrc` 文件作为凭据并跟踪 HTTP 重定向时，curl 可能在某些情况下会将用于第一个主机的密码泄漏给后续主机。只有当 netrc 文件中的条目与重定向目标主机名相匹配，但该条目要么只省略了密码，要么同时省略了登录名和密码时，该漏洞才会出现。(CVE-2024-11053)

  - 问题摘要： ECDSA 签名计算中存在时序边信道，可能允许恢复私钥。影响摘要： ECDSA 签名计算中的时序边信道可以让攻击者恢复私钥。但是，测量时序需要对签名应用程序进行本地访问，或者需要具有低延迟且非常快速的网络连接。当 top word ofthe inverted ECDSA nonce 值为 0 时，会出现约 300 纳秒的计时信号。只有在某些受支持的椭圆曲线上发生这种情况的可能性才较大。尤其是 NIST P-521 曲线会受到影响。为了能够测量此泄漏，攻击者进程必须位于同一台物理计算机中，或必须具有低延迟的极快网络连接。因此，此漏洞的严重性为低危。3.4、3.3、3.2、3.1 和 3.0 中的 FIPS 模块受此问题影响。(CVE-2024-13176)

  - libcurl 的 ASN1 解析器具有用于解析 ASN.1 UTF-8 字符串的 utf8asn1str() 函数。它可以检测无效的字段并返回错误。但这样做会在 4 字节本地堆栈缓冲区中调用“free()”。大部分现代 malloc 实现会检测到此错误并立即中止。但是，有些接受输入指针并将该内存添加到其可用区块列表中。这会导致覆盖附近的堆栈内存。覆盖的内容由“free()”实现决定；可能是内存指针和一组标记。利用此缺陷的最可能结果是崩溃，尽管不排除在特殊情况下可以造成更严重结果的可能性。(CVE-2024-6197)

  - libcurl 的 URL API 函数 [curl_url_get()](https://curl.se/libcurl/c/curl_url_get.html) 提供 punycode 与 IDN 之间的转换。在使用 *macidn* IDN 后端时，libcurl 在要求转换正好为 256 字节的名称时，最终会读取基于堆栈的缓冲区之外的内容。然后，转换函数会准确填充所提供的缓冲区，但不会对字符串进行空值终止。此缺陷可导致堆栈内容意外作为已转换字符串的一部分返回。(CVE-2024-6874)

  - libcurl 的 ASN1 解析器代码包含 `GTime2str()` 函数，用于解析 ASN.1 通用时间字段。如果给定语法上不正确的字段，解析器最终可能会使用 -1 作为
    *时间部分*的长度，从而导致对指向非（特意）以 NULL 结尾的堆缓冲区区域的指针执行 `strlen()`。此缺陷最有可能造成系统崩溃，但如果使用 [CURLINFO_CERTINFO](https://curl.se/libcurl/c/CURLINFO_CERTINFO.html)，也会导致系统将堆内容返回给应用程序。(CVE-2024-7264)

  - curl 需要使用证书状态请求 TLS 扩展（通常称为“OCSP Stapling”）来验证服务器证书是否有效时，可能无法检测一些 OCSP 问题，而是误将响应视为正常。如果返回的状态报告除“已撤销”错误之外的其他错误（例如“未经授权”），则不会将其视为不良证书。(CVE-2024-8096)

  - 当要求使用 `.netrc` 文件作为凭据 ** 和 ** 跟踪 HTTP 重定向时，curl 可能在某些情况下会将用于第一个主机的密码泄漏给后续主机。此缺陷仅在 netrc 文件具有会忽略登录名和密码的“default”条目时自行出现。罕见情况。(CVE-2025-0167)

  - 在完成线程名称解析之后断开连接通道时，libcurl 会两次错误地关闭相同的 eventfd 文件描述符。(CVE-2025-0665)

  - 当要求 libcurl 对使用 `CURLOPT_ACCEPT_ENCODING` 选项的内容编码的 HTTP 响应执行自动 gzip 解压缩时，**使用 zlib 1.2.0.3 或更早版本**，由攻击者控制的整数溢出漏洞会使 libcurl 执行缓冲区溢出。(CVE-2025-0725)

  - 在 PHP 中，8.1之前的 8.1.32.*、8.2.28 之前的 8.2.*、8.3.19 之前的 8.3.* 、8.4.5 之前的 8.4.* 在 http 请求模块解析从服务器获取的 HTTP 响应时，折叠标头解析不正确，这可能导致曲解响应和使用错误的标头、MIME 类型等。
    (CVE-2025-1217)

  在 PHP 中，8.1之前的 8.1.32.*、8.2.28 之前的 8.2.*、8.3.19 之前的 8.3.* 、8.4.5 之前的 8.4.*，使用 DOM 或 SimpleXML 扩展请求 HTTP 资源时，如果所请求的资源执行重定向，则错误的“content-type”标头会用于确定字符集。这可能造成错误地解析生成的文档或绕过验证。(CVE-2025-1219)

  - 在 PHP 中，8.1之前的 8.1.32.*、8.2.28 之前的 8.2.*、8.3.19 之前的 8.3.* 、8.4.5 之前的 8.4.*，从 HTTP 服务器接收标头时，标头缺少冒号 (:) 的电子邮件标题被视为有效标头，即使它们不是有效标头。这可使应用程序混淆而接受无效标头。
    (CVE-2025-1734)

  - 在 PHP 中，8.1之前的 8.1.32.*、8.2.28 之前的 8.2.*、8.3.19 之前的 8.3.* 、8.4.5 之前的 8.4.*，发送用户提供的标头时，不充分验证的行尾字符可能会阻止发送某些标头或导致某些标头被错误解释。(CVE-2025-1736)

  - 在 PHP 中，8.1之前的 8.1.32.*、8.2.28 之前的 8.2.*、8.3.19 之前的 8.3.* 、8.4.5 之前的 8.4.*，解析 HTTP 请求的响应中的 HTTP 重定向时中，当前存在位置值大小的限制，这是因为位置缓冲区的大小不能超过 1024 而造成的。然而，根据 RFC9110，建议将限制设为 8000。这可导致错误的 URL 截断和重定向到错误的位置。(CVE-2025-1861)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 问题摘要： ECDSA 签名计算中存在时序边信道，可能允许恢复私钥。影响摘要： ECDSA 签名计算中的时序边信道可以让攻击者恢复私钥。但是，测量时序需要对签名应用程序进行本地访问，或者需要具有低延迟且非常快速的网络连接。当 top word ofthe inverted ECDSA nonce 值为 0 时，会出现约 300 纳秒的计时信号。只有在某些受支持的椭圆曲线上发生这种情况的可能性才较大。尤其是 NIST P-521 曲线会受到影响。为了能够测量此泄漏，攻击者进程必须位于同一台物理计算机中，或必须具有低延迟的极快网络连接。因此，此漏洞的严重性为低危。3.4、3.3、3.2、3.1 和 3.0 中的 FIPS 模块受此问题影响。(CVE-2024-13176)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

It is, therefore, affected by a vulnerability as referenced in the ALAS2-2025-2750 advisory.

    Issue summary: A timing side-channel which could potentially allow recoveringthe private key exists in the     ECDSA signature computation.

    Impact summary: A timing side-channel in ECDSA signature computationscould allow recovering the private     key by an attacker. However, measuringthe timing would require either local access to the signing     application ora very fast network connection with low latency.

    There is a timing signal of around 300 nanoseconds when the top word ofthe inverted ECDSA nonce value is     zero. This can happen with significantprobability only for some of the supported elliptic curves. In     particularthe NIST P-521 curve is affected. To be able to measure this leak, the attackerprocess must     either be located in the same physical computer or musthave a very fast network connection with low     latency. For that reasonthe severity of this vulnerability is Low. (CVE-2024-13176)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:0388-1 advisory.

    - CVE-2024-13176: Fixed timing side-channel in ECDSA signature computation (bsc#1236136).

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

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:0356-1 advisory.

    - CVE-2024-13176: Fixed timing side-channel in the ECDSA signature computation (bsc#1236136)

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

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

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

    - CVE-2024-13176: Fixed timing side-channel in the ECDSA signature computation (bsc#1236136)

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

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

The version of openssl-snapsafe installed on the remote host is prior to 1.0.2k-24. It is, therefore, affected by a vulnerability as referenced in the ALAS2OPENSSL-SNAPSAFE-2025-007 advisory.

    Issue summary: A timing side-channel which could potentially allow recoveringthe private key exists in the     ECDSA signature computation.

    Impact summary: A timing side-channel in ECDSA signature computationscould allow recovering the private     key by an attacker. However, measuringthe timing would require either local access to the signing     application ora very fast network connection with low latency.

    There is a timing signal of around 300 nanoseconds when the top word ofthe inverted ECDSA nonce value is     zero. This can happen with significantprobability only for some of the supported elliptic curves. In     particularthe NIST P-521 curve is affected. To be able to measure this leak, the attackerprocess must     either be located in the same physical computer or musthave a very fast network connection with low     latency. For that reasonthe severity of this vulnerability is Low. (CVE-2024-13176)

Tenable has extracted the preceding description block directly from the tested product 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 openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    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.(CVE-2024-13176)

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

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

The version of edk2 / openssl installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-13176 advisory.

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

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

The version of edk2 / openssl installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-13176 advisory.

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

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

The remote Debian 11 host has packages installed that are affected by a vulnerability as referenced in the dla-4176 advisory.

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-4176-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                          Adrian Bunk     May 24, 2025                                  https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : openssl     Version        : 1.1.1w-0+deb11u3     CVE ID         : CVE-2024-13176     Debian Bug     : 1094027

    A timing side-channel in ECDSA signature computation has been fixed in     the cryptography library OpenSSL.

    For Debian 11 bullseye, this problem has been fixed in version     1.1.1w-0+deb11u3.

    We recommend that you upgrade your openssl packages.

    For the detailed security status of openssl please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/openssl

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS

Tenable has extracted the preceding description block directly from the Debian 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 its self-reported version, the Nessus Network Monitor running on the remote host is prior to 6.5.1. It is, therefore, affected by multiple vulnerabilities as referenced in the TNS-2025-10 advisory.

  - In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a     heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML     schema with certain identity constraints, or a crafted XML schema must be used. (CVE-2025-32415)

  - When installing Tenable Network Monitor to a non-default location on a Windows host, Tenable Network     Monitor versions prior to 6.5.1 did not enforce secure permissions for sub-directories. This could allow     for local privilege escalation if users had not secured the directories in the non-default installation     location. (CVE-2025-24916)

  - In Tenable Network Monitor versions prior to 6.5.1 on a Windows host, it was found that a     non-administrative user could stage files in a local directory to run arbitrary code with SYSTEM     privileges, potentially leading to local privilege escalation. (CVE-2025-24917)

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 tongsuo packages installed that are affected by multiple vulnerabilities:

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

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

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

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.

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

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

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
234507	Tenable Security Center 多个漏洞 (TNS-2025-04)	Nessus	Misc.	2025/4/16	2025/4/16	high
228225	Linux Distros 未修补的漏洞：CVE-2024-13176	Nessus	Misc.	2025/3/5	2025/9/20	medium
214984	Amazon Linux 2 : edk2 (ALAS-2025-2750)	Nessus	Amazon Linux Local Security Checks	2025/2/4	2025/2/4	medium
215173	SUSE SLES15 Security Update : openssl-3 (SUSE-SU-2025:0388-1)	Nessus	SuSE Local Security Checks	2025/2/10	2025/5/23	medium
215183	SUSE SLES15 Security Update : openssl-1_1 (SUSE-SU-2025:0356-1)	Nessus	SuSE Local Security Checks	2025/2/10	2025/5/23	medium
216201	SUSE SLES12 Security Update : openssl-1_1 (SUSE-SU-2025:0390-1)	Nessus	SuSE Local Security Checks	2025/2/12	2025/5/23	medium
232227	Amazon Linux 2 : openssl-snapsafe (ALASOPENSSL-SNAPSAFE-2025-007)	Nessus	Amazon Linux Local Security Checks	2025/3/6	2025/3/6	medium
233608	EulerOS 2.0 SP13 : openssl (EulerOS-SA-2025-1321)	Nessus	Huawei Local Security Checks	2025/4/1	2025/5/23	medium
233616	EulerOS 2.0 SP13 : openssl (EulerOS-SA-2025-1338)	Nessus	Huawei Local Security Checks	2025/4/1	2025/5/23	medium
234631	CBL Mariner 2.0 Security Update: edk2 / openssl (CVE-2024-13176)	Nessus	MarinerOS Local Security Checks	2025/4/19	2025/5/23	medium
234632	Azure Linux 3.0 Security Update: edk2 / openssl (CVE-2024-13176)	Nessus	Azure Linux Local Security Checks	2025/4/19	2025/9/15	medium
237256	Debian dla-4176 : libcrypto1.1-udeb - security update	Nessus	Debian Local Security Checks	2025/5/26	2025/5/26	medium
237289	Nessus Network Monitor < 6.5.1 Multiple Vulnerabilities (TNS-2025-10)	Nessus	Misc.	2025/5/27	2025/5/30	high
238013	NewStart CGSL MAIN 7.02 : tongsuo Multiple Vulnerabilities (NS-SA-2025-0075)	Nessus	NewStart CGSL Local Security Checks	2025/6/9	2025/6/18	high
234507	Tenable Security Center Multiple Vulnerabilities (TNS-2025-04)	Nessus	Misc.	2025/4/16	2025/4/16	high
228225	Linux Distros Unpatched Vulnerability : CVE-2024-13176	Nessus	Misc.	2025/3/5	2025/9/20	medium

偵測

搜尋 Plugin

high

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

high

high

high

medium