The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1780683040 advisory.

  - In order to decrypt SM2 encrypted data an application is expected to call the API function     EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the     out parameter can be NULL and, on exit, the outlen parameter is populated with the buffer size     required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer     and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the out parameter. A bug     in the implementation of the SM2 decryption code means that the calculation of the buffer size required to     hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size     required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the     application a second time with a buffer that is too small. A malicious attacker who is able present SM2     content for decryption to an application could cause attacker chosen data to overflow the buffer by up to     a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing     application behaviour or causing the application to crash. The location of the buffer is application     dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).
    (CVE-2021-3711)

  - If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a     write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results     in a denial of service when the affected process hangs. Policy processing being enabled on a publicly     facing server is not considered to be a common setup. Policy processing is enabled by passing the     `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()'     function. Update (31 March 2023): The description of the policy processing enablement was corrected based     on CVE-2023-0466. (CVE-2022-3996)

  - Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client     protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer     overread can have a range of potential consequences such as unexpected application beahviour or a crash.
    In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent     to the peer leading to a loss of confidentiality. However, only applications that directly call the     SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this     issue. This would normally never be a valid scenario and is typically not under attacker control but may     occur by accident in the case of a configuration or programming error in the calling application. The     OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN     (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never     standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely     deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a     list of protocols from the client and returns the first protocol that appears in the server list that also     appears in the client list. In the case of no overlap between the two lists it returns the first item in     the client list. In either case it will signal whether an overlap between the two lists was found. In the     case where SSL_select_next_proto is called with a zero length client list it fails to notice this     condition and returns the memory immediately following the client list pointer (and reports that there was     no overlap in the lists). This function is typically called from a server side application callback for     ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by     the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the     application and should never normally be expected to be of zero length. In this case if the     SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in     the client/client_len parameters), then the application will not be vulnerable to this issue. If the     application has accidentally been configured with a zero length server list, and has accidentally passed     that zero length server list in the client/client_len parameters, and has additionally failed to correctly     handle a no overlap response (which would normally result in a handshake failure in ALPN) then it will     be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically     select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap     case in support of this. The list of client protocols comes from the application and should never normally     be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called     with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses     this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been     assessed as Low severity because applications are most likely to be vulnerable if they are using NPN     instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming     error. Finally, this issue would not typically be under attacker control making active exploitation     unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low     severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included     in the next releases when they become available. (CVE-2024-5535)

  - 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: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the     PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash     which leads to Denial of Service for an application processing PKCS#12 files. The     PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before     dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter     can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to     achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a     malformed PKCS#12 file to an application that processes it. 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, 1.1.1 and 1.0.2 are vulnerable to this issue. (CVE-2025-69421)

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

Detections

Analytics

CentOS Linux 7 [TuxCare] Security Update: openssl11 / openssl11-devel / openssl11-libs / openssl11-static Multiple Vulnerabilities (CENTOS7:CLSA-2026:1780683040)

high Nessus Plugin ID 361388

Version 1.2

Version 1.1

Version 1.2 Oct 20, 2026, 4:30 AM CVE (set "CVE" coverage to "CVE-2021-3711,CVE-2022-3996,CVE-2023-0464,CVE-2024-5535,CVE-2025-69419,CVE-2025-69421,CVE-2026-28387,CVE-2026-28388,CVE-2026-28389,CVE-2026-28390") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610200430
Version 1.1 Oct 1, 2026, 9:59 PM New Plugin Feed: 202610012159