The version of OpenSSL installed on the remote host is prior to 1.1.1zg. It is, therefore, affected by multiple vulnerabilities as referenced in the 1.1.1zg advisory.

  - Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when     paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the     client side.  Impact summary: A use after free can have a range of potential consequences such as the     corruption of valid data, crashes or execution of arbitrary code.  However, the issue only affects clients     that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2)     certificate usage.  By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends     that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages.  These SMTP (or     other similar) clients are not vulnerable to this issue.  Conversely, any clients that support only the     PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.  The client would also need to be     communicating with a server that publishes a TLSA RRset with both types of TLSA records.  No FIPS modules     are affected by this issue, the problem code is outside the FIPS module boundary. Fixed in OpenSSL 1.1.1zg     (Affected since 1.1.1). (CVE-2026-28387)

  - Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a     NULL pointer dereference can happen.  Impact summary: Applications that process attacker-controlled CMS     data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
    When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is     processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without     checking for its presence. This results in a NULL pointer dereference if the field is missing.
    Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based     protocols) are vulnerable.  The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,     as the affected code is outside the OpenSSL FIPS module boundary. Fixed in OpenSSL 1.1.1zg (Affected since     1.1.1). (CVE-2026-28390)

  - Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL     pointer dereference can happen.  Impact summary: Applications that process attacker-controlled CMS data     may crash before authentication or cryptographic operations occur resulting in Denial of Service.  When a     CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of     KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL     pointer dereference if the field is missing.  Applications and services that call CMS_decrypt() on     untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.  The FIPS modules in 3.6,     3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS     module boundary. Fixed in OpenSSL 1.1.1zg (Affected since 1.1.1). (CVE-2026-28389)

  - Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer     dereference might happen if the required CRL Number extension is missing.  Impact summary: A NULL pointer     dereference can trigger a crash which leads to a Denial of Service for an application.  When CRL     processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL     processing does not check whether the CRL Number extension is NULL before dereferencing it. When a     malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer     dereference.  Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the     verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to     have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that     processes it.  The vulnerability is limited to Denial of Service and cannot be escalated to achieve code     execution or memory disclosure. For that reason the issue was assessed as Low severity according to our     Security Policy.  The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the     affected code is outside the OpenSSL FIPS module boundary. Fixed in OpenSSL 1.1.1zg (Affected since     1.1.1). (CVE-2026-28388)

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 openssl11 installed on the remote host is prior to 1.1.1zg-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-3249 advisory.

    Potential use-after-free in DANE client code (CVE-2026-28387)

    NULL Pointer Dereference When Processing a Delta CRL

    NOTE: https://openssl-library.org/news/secadv/20260407.txt (CVE-2026-28388)

    Possible NULL dereference when processing CMS KeyAgreeRecipientInfo (CVE-2026-28389)

    Possible NULL dereference when processing CMS KeyTransportRecipientInfo (CVE-2026-28390)

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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:1375-1 advisory.

    Security issues fixed:

    - CVE-2026-28387: Potential use-after-free in DANE client code (bsc#1260441).
    - CVE-2026-28388: NULL Pointer Dereference When Processing a Delta CRL (bsc#1260442).
    - CVE-2026-28389: Possible NULL dereference when processing CMS KeyAgreeRecipientInfo (bsc#1260443).
    - CVE-2026-31789: Heap buffer overflow in hexadecimal conversion (bsc#1260444).
    - CVE-2026-31790: Incorrect failure handling in RSA KEM RSASVE encapsulation (bsc#1260445).
    - CVE-2026-28390: NULL pointer dereference during processing of a crafted CMS EnvelopedData message with       KeyTransportRecipientInfo (bsc#1261678).

    Other updates and bugfixes:

    - Enable MD2 in legacy provider (jsc#PED-15724).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:1577-1 advisory.

    - CVE-2026-28387: Potential use-after-free in DANE client code (bsc#1260441).
    - CVE-2026-28388: NULL Pointer Dereference When Processing a Delta CRL (bsc#1260442).
    - CVE-2026-28389: Possible NULL dereference when processing CMS KeyAgreeRecipientInfo (bsc#1260443).
    - CVE-2026-28390: NULL pointer dereference during processing of a crafted CMS EnvelopedData message with       KeyTransportRecipientInfo (bsc#1261678).
    - CVE-2026-31789: Heap buffer overflow in hexadecimal conversion (bsc#1260444).

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

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 openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Applications using RSASVE key encapsulation to establish_x000D_     a secret encryption key can send contents of an uninitialized memory buffer to_x000D_     a malicious peer._x000D_
    _x000D_     Impact summary: The uninitialized buffer might contain sensitive data from the_x000D_     previous execution of the application process which leads to sensitive data_x000D_     leakage to an attacker._x000D_
    _x000D_     RSA_public_encrypt() returns the number of bytes written on success and -1_x000D_     on error. The affected code tests only whether the return value is non-zero._x000D_     As a result, if RSA encryption fails, encapsulation can still return success to_x000D_     the caller, set the output lengths, and leave the caller to use the contents of_x000D_     the ciphertext buffer as if a valid KEM ciphertext had been produced._x000D_
    _x000D_     If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an_x000D_     attacker-supplied invalid RSA public key without first validating that key,_x000D_     then this may cause stale or uninitialized contents of the caller-provided_x000D_     ciphertext buffer to be disclosed to the attacker in place of the KEM_x000D_     ciphertext._x000D_
    _x000D_     As a workaround calling EVP_PKEY_public_check() or_x000D_     EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate_x000D_     the issue._x000D_
    _x000D_     The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.(CVE-2026-31790)

    Issue summary: An uncommon configuration of clients performing DANE TLSA-based_x000D_     server authentication, when paired with uncommon server DANE TLSA records, may_x000D_     result in a use-after-free and/or double-free on the client side._x000D_
    _x000D_     Impact summary: A use after free can have a range of potential consequences_x000D_     such as the corruption of valid data, crashes or execution of arbitrary code._x000D_
    _x000D_     However, the issue only affects clients that make use of TLSA records with both_x000D_     the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate_x000D_     usage._x000D_
    _x000D_     By far the most common deployment of DANE is in SMTP MTAs for which RFC7672_x000D_     recommends that clients treat as 'unusable' any TLSA records that have the PKIX_x000D_     certificate usages.  These SMTP (or other similar) clients are not vulnerable_x000D_     to this issue.  Conversely, any clients that support only the PKIX usages, and_x000D_     ignore the DANE-TA(2) usage are also not vulnerable._x000D_
    _x000D_     The client would also need to be communicating with a server that publishes a_x000D_     TLSA RRset with both types of TLSA records._x000D_
    _x000D_     No FIPS modules are affected by this issue, the problem code is outside the_x000D_     FIPS module boundary.(CVE-2026-28387)

    Issue summary: When a delta CRL that contains a Delta CRL Indicator extension_x000D_     is processed a NULL pointer dereference might happen if the required CRL_x000D_     Number extension is missing._x000D_
    _x000D_     Impact summary: A NULL pointer dereference can trigger a crash which_x000D_     leads to a Denial of Service for an application._x000D_
    _x000D_     When CRL processing and delta CRL processing is enabled during X.509_x000D_     certificate verification, the delta CRL processing does not check_x000D_     whether the CRL Number extension is NULL before dereferencing it._x000D_     When a malformed delta CRL file is being processed, this parameter_x000D_     can be NULL, causing a NULL pointer dereference._x000D_
    _x000D_     Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in_x000D_     the verification context, the certificate being verified to contain a_x000D_     freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and_x000D_     an attacker to provide a malformed CRL to an application that processes it._x000D_
    _x000D_     The vulnerability is limited to Denial of Service and cannot be escalated to_x000D_     achieve code execution or memory disclosure. For that reason the issue was_x000D_     assessed as Low severity according to our Security Policy._x000D_
    _x000D_     The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,_x000D_     as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28388)

    Issue summary: Converting an excessively large OCTET STRING value to_x000D_     a hexadecimal string leads to a heap buffer overflow on 32 bit platforms._x000D_
    _x000D_     Impact summary: A heap buffer overflow may lead to a crash or possibly_x000D_     an attacker controlled code execution or other undefined behavior._x000D_
    _x000D_     If an attacker can supply a crafted X.509 certificate with an excessively_x000D_     large OCTET STRING value in extensions such as the Subject Key Identifier_x000D_     (SKID) or Authority Key Identifier (AKID) which are being converted to hex,_x000D_     the size of the buffer needed for the result is calculated as multiplication_x000D_     of the input length by 3. On 32 bit platforms, this multiplication may overflow_x000D_     resulting in the allocation of a smaller buffer and a heap buffer overflow._x000D_
    _x000D_     Applications and services that print or log contents of untrusted X.509_x000D_     certificates are vulnerable to this issue. As the certificates would have_x000D_     to have sizes of over 1 Gigabyte, printing or logging such certificates_x000D_     is a fairly unlikely operation and only 32 bit platforms are affected,_x000D_     this issue was assigned Low severity._x000D_
    _x000D_     The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this_x000D_     issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-31789)

    Issue summary: During processing of a crafted CMS EnvelopedData message_x000D_     with KeyAgreeRecipientInfo a NULL pointer dereference can happen._x000D_
    _x000D_     Impact summary: Applications that process attacker-controlled CMS data may_x000D_     crash before authentication or cryptographic operations occur resulting in_x000D_     Denial of Service._x000D_
    _x000D_     When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is_x000D_     processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier_x000D_     is examined without checking for its presence. This results in a NULL_x000D_     pointer dereference if the field is missing._x000D_
    _x000D_     Applications and services that call CMS_decrypt() on untrusted input_x000D_     (e.g., S/MIME processing or CMS-based protocols) are vulnerable._x000D_
    _x000D_     The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this_x000D_     issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28389)

    Issue summary: During processing of a crafted CMS EnvelopedData message_x000D_     with KeyTransportRecipientInfo a NULL pointer dereference can happen._x000D_
    _x000D_     Impact summary: Applications that process attacker-controlled CMS data may_x000D_     crash before authentication or cryptographic operations occur resulting in_x000D_     Denial of Service._x000D_
    _x000D_     When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with_x000D_     RSA-OAEP encryption is processed, the optional parameters field of_x000D_     RSA-OAEP SourceFunc algorithm identifier is examined without checking_x000D_     for its presence. This results in a NULL pointer dereference if the field_x000D_     is missing._x000D_
    _x000D_     Applications and services that call CMS_decrypt() on untrusted input_x000D_     (e.g., S/MIME processing or CMS-based protocols) are vulnerable._x000D_
    _x000D_     The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this_x000D_     issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28390)

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

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 openssl packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    Issue summary: An uncommon configuration of clients performing DANE TLSA-based     server authentication, when paired with uncommon server DANE TLSA records, may     result in a use-after-free and/or double-free on the client side.

    Impact summary: A use after free can have a range of potential consequences     such as the corruption of valid data, crashes or execution of arbitrary code.

    However, the issue only affects clients that make use of TLSA records with both     the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate     usage.

    By far the most common deployment of DANE is in SMTP MTAs for which RFC7672     recommends that clients treat as 'unusable' any TLSA records that have the PKIX     certificate usages.  These SMTP (or other similar) clients are not vulnerable     to this issue.  Conversely, any clients that support only the PKIX usages, and     ignore the DANE-TA(2) usage are also not vulnerable.

    The client would also need to be communicating with a server that publishes a     TLSA RRset with both types of TLSA records.

    No FIPS modules are affected by this issue, the problem code is outside the     FIPS module boundary.(CVE-2026-28387)

    Issue summary: When a delta CRL that contains a Delta CRL Indicator extension     is processed a NULL pointer dereference might happen if the required CRL     Number extension is missing.

    Impact summary: A NULL pointer dereference can trigger a crash which     leads to a Denial of Service for an application.

    When CRL processing and delta CRL processing is enabled during X.509     certificate verification, the delta CRL processing does not check     whether the CRL Number extension is NULL before dereferencing it.
    When a malformed delta CRL file is being processed, this parameter     can be NULL, causing a NULL pointer dereference.

    Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in     the verification context, the certificate being verified to contain a     freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and     an attacker to provide a malformed CRL to an application that processes it.

    The vulnerability is limited to Denial of Service and cannot be escalated to     achieve code execution or memory disclosure. For that reason the issue was     assessed as Low severity according to our Security Policy.

    The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,     as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28388)

    Issue summary: During processing of a crafted CMS EnvelopedData message     with KeyAgreeRecipientInfo a NULL pointer dereference can happen.

    Impact summary: Applications that process attacker-controlled CMS data may     crash before authentication or cryptographic operations occur resulting in     Denial of Service.

    When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is     processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier     is examined without checking for its presence. This results in a NULL     pointer dereference if the field is missing.

    Applications and services that call CMS_decrypt() on untrusted input     (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

    The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this     issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28389)

    Issue summary: During processing of a crafted CMS EnvelopedData message     with KeyTransportRecipientInfo a NULL pointer dereference can happen.

    Impact summary: Applications that process attacker-controlled CMS data may     crash before authentication or cryptographic operations occur resulting in     Denial of Service.

    When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with     RSA-OAEP encryption is processed, the optional parameters field of     RSA-OAEP SourceFunc algorithm identifier is examined without checking     for its presence. This results in a NULL pointer dereference if the field     is missing.

    Applications and services that call CMS_decrypt() on untrusted input     (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

    The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this     issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-28390)

Tenable has extracted the preceding description block directly from the EulerOS openssl 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 tongsuo packages installed that are affected by multiple vulnerabilities:

 - Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable. The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records. No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary. (CVE-2026-28387)

 - Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of- bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application. The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2025-68160)

 - Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated. Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection. The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes. However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware- accelerated builds. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as OCB mode is not a FIPS- approved algorithm. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue. (CVE-2025-69418)

 - Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
 The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker- controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
 (CVE-2025-69419)

 - Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue. (CVE-2025-69420)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
305204	OpenSSL 1.1.1 < 1.1.1zg Multiple Vulnerabilities	Nessus	Web Servers	2026/4/7	2026/4/27	high
306295	Amazon Linux 2 : openssl11, --advisory ALAS2-2026-3249 (ALAS-2026-3249)	Nessus	Amazon Linux Local Security Checks	2026/4/14	2026/5/5	high
306876	SUSE SLED15 / SLES15 Security Update : openssl-3 (SUSE-SU-2026:1375-1)	Nessus	SuSE Local Security Checks	2026/4/17	2026/4/27	critical
310064	SUSE SLES15 Security Update : openssl-1_1 (SUSE-SU-2026:1577-1)	Nessus	SuSE Local Security Checks	2026/4/24	2026/4/24	critical
323177	EulerOS 2.0 SP15 : openssl (EulerOS-SA-2026-2456)	Nessus	Huawei Local Security Checks	2026/6/27	2026/6/27	critical
326651	EulerOS 2.0 SP10 : openssl (EulerOS-SA-2026-2665)	Nessus	Huawei Local Security Checks	2026/7/14	2026/7/14	high
343598	NewStart CGSL MAIN 7.02 : tongsuo Multiple Vulnerabilities (NS-SA-2026-0106)	Nessus	NewStart CGSL Local Security Checks	2026/9/8	2026/9/8	high

检测

插件搜索

high

high

critical

critical

critical

high

high