Alpine: libcrypto3, multiple openssl packages: security update to 3.3.6-r0

high Tenable Self-Hosted Container Security Plugin ID 437124

Description

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

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

- Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD
parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a
crash, causing Denial of Service, or potentially remote code execution. When parsing CMS
(Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector)
encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length
fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-
based out-of-bounds write before any authentication or tag verification occurs. Applications and services
that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-
GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is
required to trigger it. While exploitability to remote code execution depends on platform and toolchain
mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4,
3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module
boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not
affected by this issue. (CVE-2025-15467)

- Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server
receives an unknown cipher suite from the peer, a NULL dereference occurs. Impact summary: A NULL pointer
dereference leads to abnormal termination of the running process causing Denial of Service. Some
applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the
peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will
happen if the examined cipher ID is unknown or unsupported. As it is not very common to call this function
in applications using the QUIC protocol and the worst outcome is Denial of Service, the issue was assessed
as Low severity. The vulnerable code was introduced in the 3.2 version with the addition of the QUIC
protocol support. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the QUIC
implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable
to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-15468)

- Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer
before decompression without checking against the configured certificate size limit. Impact summary: An
attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work,
potentially leading to service degradation or resource exhaustion (Denial of Service). In affected
configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is
used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list
setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large
per-connection allocations followed by handshake failure. No memory corruption or information disclosure
occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not
OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and
where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and
servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not
request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue
by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS
modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the
OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0,
1.1.1 and 1.0.2 are not affected by this issue. (CVE-2025-66199)

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

Plugin Details

Severity: High

ID: 437124

Version: Revision 1.13

Type: Local

Family: Alpine Linux Local Security Checks

Published: 1/27/2026

Updated: 7/2/2026

Supported Sensors: Agentless Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: High

Score: 7.9

Percentile: 99.36

CVSS v2

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.1

Vector: CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:C

CVSS Score Source: CVE-2025-69421

CVSS v3

Risk Factor: High

Base Score: 7.5

Temporal Score: 6.7

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C

Vulnerability Information

Exploit Available: true

Exploit Ease: Exploits are available

Reference Information

CVE: CVE-2025-15467, CVE-2025-15468, CVE-2025-66199, CVE-2025-68160, CVE-2025-69418, CVE-2025-69419, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796

Detections

Analytics

Alpine: libcrypto3, multiple openssl packages: security update to 3.3.6-r0

high Tenable Self-Hosted Container Security Plugin ID 437124

Description

See Also

Plugin Details

Risk Information

VPR

CVSS v2

CVSS v3

Vulnerability Information

Reference Information