Detections
Analytics

Alpine: openssl: security update to 3.0.8-r0

critical Tenable Self-Hosted Container Security Plugin ID 406121

Description

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

 - There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName.
 X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME
 incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently
 interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL
 checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may
 allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or
 enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate
 chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these
 inputs, the other input must already contain an X.400 address as a CRL distribution point, which is
 uncommon. As such, this vulnerability is most likely to only affect applications which have implemented
 their own functionality for retrieving CRLs over a network. (CVE-2023-0286)

 - A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint
 checking. Note that this occurs after certificate chain signature verification and requires either a CA to
 have signed the malicious certificate or for the application to continue certificate verification despite
 failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which
 could lead to a denial of service attack. In theory it could also result in the disclosure of private
 memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working
 exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client,
 this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the
 server requests client authentication and a malicious client connects. (CVE-2022-4203)

 - A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient
 to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful
 decryption an attacker would have to be able to send a very large number of trial messages for decryption.
 The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS
 connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An
 attacker that had observed a genuine connection between a client and a server could use this flaw to send
 trial messages to the server and record the time taken to process them. After a sufficiently large number
 of messages the attacker could recover the pre-master secret used for the original connection and thus be
 able to decrypt the application data sent over that connection. (CVE-2022-4304)

 - The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g.
 "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out",
 "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data.
 The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results
 in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate
 the header argument with a pointer to a buffer that has already been freed. If the caller also frees this
 buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an
 attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service
 attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and
 therefore these functions are also directly affected. These functions are also called indirectly by a
 number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file()
 which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the
 caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations
 include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL
 asn1parse command line application is also impacted by this issue. (CVE-2022-4450)

 - The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is
 primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may
 also be called directly by end user applications. The function receives a BIO from the caller, prepends a
 new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the
 BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid,
 the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this
 case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal
 pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then
 a use-after-free will occur. This will most likely result in a crash. This scenario occurs directly in the
 internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call
 BIO_pop() on the BIO. This internal function is in turn called by the public API functions
 PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1,
 SMIME_write_CMS and SMIME_write_PKCS7. Other public API functions that may be impacted by this include
 i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream. The OpenSSL
 cms and smime command line applications are similarly affected. (CVE-2023-0215)

See Also

https://security.alpinelinux.org/vuln/CVE-2022-4203

https://security.alpinelinux.org/vuln/CVE-2022-4304

https://security.alpinelinux.org/vuln/CVE-2022-4450

https://security.alpinelinux.org/vuln/CVE-2023-0215

https://security.alpinelinux.org/vuln/CVE-2023-0216

https://security.alpinelinux.org/vuln/CVE-2023-0217

https://security.alpinelinux.org/vuln/CVE-2023-0286

https://security.alpinelinux.org/vuln/CVE-2023-0401

Plugin Details

Severity: Critical

ID: 406121

Version: Revision 1.36

Type: Local

Published: 10/31/2023

Updated: 9/29/2025

Supported Sensors: Agentless Assessment

Risk Information

VPR

Risk Factor: High

Score: 7

Percentile: 98.33

CVSS v2

Risk Factor: High

Base Score: 7.1

Temporal Score: 5.3

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

CVSS Score Source: CVE-2023-0286

CVSS v3

Risk Factor: High

Base Score: 7.4

Temporal Score: 6.4

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

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

CVSS v4

Risk Factor: Critical

Base Score: 9.3

Threat Score: 8.1

Threat Vector: CVSS:4.0/E:U

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS Score Source: CVE-2023-0401

Vulnerability Information

Exploit Ease: No known exploits are available

Vulnerability Publication Date: 12/15/2022

Reference Information

CVE: CVE-2022-4203, CVE-2022-4304, CVE-2022-4450, CVE-2023-0215, CVE-2023-0216, CVE-2023-0217, CVE-2023-0286, CVE-2023-0401

IAVA: 2022-A-0518-S, 2023-A-0462-S, 2023-A-0582-S