Alpine: openssl3: security update to 3.0.3-r0

medium Tenable Cloud Security Plugin ID 406166

Description

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

- The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where
the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful
verification) even in the case where the response signing certificate fails to verify. It is anticipated
that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the
`OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a
certificate verification failure. The normal expected return value in this case would be 0. This issue
also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the
"-no_cert_checks" option the command line application will report that the verification is successful even
though it has in fact failed. In this case the incorrect successful response will also be accompanied by
error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL
3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1343)

- The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.
This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-
the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the
modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint
to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at
that point. Many application protocols require data to be sent from the client to the server first.
Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0
client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both
directions. In this case both clients and servers could be affected, regardless of the application
protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint
communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this
ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt
data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to
work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled
by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite
list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0
endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with
the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider
explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been
explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is
1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the
RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3
(Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1434)

- The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the
memory occuppied by the removed hash table entries. This function is used when decoding certificates or
keys. If a long lived process periodically decodes certificates or keys its memory usage will expand
without bounds and the process might be terminated by the operating system causing a denial of service.
Also traversing the empty hash table entries will take increasingly more time. Typically such long lived
processes might be TLS clients or TLS servers configured to accept client certificate authentication. The
function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in
OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). (CVE-2022-1473)

Plugin Details

Severity: Medium

ID: 406166

Version: Revision 1.25

Type: Local

Family: Alpine Linux Local Security Checks

Published: 10/31/2023

Updated: 7/2/2026

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

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.18

CVSS v2

Risk Factor: Medium

Base Score: 4.3

Temporal Score: 3.2

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

CVSS Score Source: CVE-2022-1434

CVSS v3

Risk Factor: Medium

Base Score: 5.9

Temporal Score: 5.2

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

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

Vulnerability Information

Exploit Ease: No known exploits are available

Vulnerability Publication Date: 5/3/2022

Reference Information

CVE: CVE-2022-1343, CVE-2022-1434, CVE-2022-1473

IAVA: 2022-A-0186-S

Detections

Analytics