Headline
Gentoo Linux Security Advisory 202301-08
Gentoo Linux Security Advisory 202301-8 - Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could result in arbitrary code execution. Versions less than 2.28.1 are affected.
Gentoo Linux Security Advisory GLSA 202301-08
https://security.gentoo.org/
Severity: Normal
Title: Mbed TLS: Multiple Vulnerabilities
Date: January 11, 2023
Bugs: #857813, #829660, #801376, #778254, #764317, #740108, #730752
ID: 202301-08
Synopsis
Multiple vulnerabilities have been discovered in Mbed TLS, the worst of
which could result in arbitrary code execution.
Background
Mbed TLS (previously PolarSSL) is an “easy to understand, use, integrate
and expand” implementation of the TLS and SSL protocols and the
respective cryptographic algorithms and support code required.
Affected packages
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-libs/mbedtls < 2.28.1 >= 2.28.1
Description
Multiple vulnerabilities have been discovered in Mbed TLS. Please review
the CVE identifiers referenced below for details.
Impact
Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.
Resolution
All Mbed TLS users should upgrade to the latest version:
emerge --sync
emerge --ask --oneshot --verbose “>=net-libs/mbedtls-2.28.1”
References
[ 1 ] CVE-2020-16150
https://nvd.nist.gov/vuln/detail/CVE-2020-16150
[ 2 ] CVE-2020-36421
https://nvd.nist.gov/vuln/detail/CVE-2020-36421
[ 3 ] CVE-2020-36422
https://nvd.nist.gov/vuln/detail/CVE-2020-36422
[ 4 ] CVE-2020-36423
https://nvd.nist.gov/vuln/detail/CVE-2020-36423
[ 5 ] CVE-2020-36424
https://nvd.nist.gov/vuln/detail/CVE-2020-36424
[ 6 ] CVE-2020-36425
https://nvd.nist.gov/vuln/detail/CVE-2020-36425
[ 7 ] CVE-2020-36426
https://nvd.nist.gov/vuln/detail/CVE-2020-36426
[ 8 ] CVE-2020-36475
https://nvd.nist.gov/vuln/detail/CVE-2020-36475
[ 9 ] CVE-2020-36476
https://nvd.nist.gov/vuln/detail/CVE-2020-36476
[ 10 ] CVE-2020-36477
https://nvd.nist.gov/vuln/detail/CVE-2020-36477
[ 11 ] CVE-2020-36478
https://nvd.nist.gov/vuln/detail/CVE-2020-36478
[ 12 ] CVE-2021-43666
https://nvd.nist.gov/vuln/detail/CVE-2021-43666
[ 13 ] CVE-2021-44732
https://nvd.nist.gov/vuln/detail/CVE-2021-44732
[ 14 ] CVE-2021-45450
https://nvd.nist.gov/vuln/detail/CVE-2021-45450
[ 15 ] CVE-2022-35409
https://nvd.nist.gov/vuln/detail/CVE-2022-35409
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202301-08
Concerns?
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users’ machines is of utmost
importance to us. Any security concerns should be addressed to
[email protected] or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
Copyright 2023 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
Related news
An issue was discovered in Mbed TLS before 2.28.2 and 3.x before 3.2.0. In some configurations, an unauthenticated attacker can send an invalid ClientHello message to a DTLS server that causes a heap-based buffer over-read of up to 255 bytes. This can cause a server crash or possibly information disclosure based on error responses. Affected configurations have MBEDTLS_SSL_DTLS_CLIENT_PORT_REUSE enabled and MBEDTLS_SSL_IN_CONTENT_LEN less than a threshold that depends on the configuration: 258 bytes if using mbedtls_ssl_cookie_check, and possibly up to 571 bytes with a custom cookie check function.
A Denial of Service vulnerability exists in mbed TLS 3.0.0 and earlier in the mbedtls_pkcs12_derivation function when an input password's length is 0.
In Mbed TLS before 2.28.0 and 3.x before 3.1.0, psa_cipher_generate_iv and psa_cipher_encrypt allow policy bypass or oracle-based decryption when the output buffer is at memory locations accessible to an untrusted application.
Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure.
An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). A NULL algorithm parameters entry looks identical to an array of REAL (size zero) and thus the certificate is considered valid. However, if the parameters do not match in any way, then the certificate should be considered invalid.
An issue was discovered in Mbed TLS before 2.24.0 (and before 2.16.8 LTS and before 2.7.17 LTS). There is missing zeroization of plaintext buffers in mbedtls_ssl_read to erase unused application data from memory.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.24.0. It incorrectly uses a revocationDate check when deciding whether to honor certificate revocation via a CRL. In some situations, an attacker can exploit this by changing the local clock.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.24.0. An attacker can recover a private key (for RSA or static Diffie-Hellman) via a side-channel attack against generation of base blinding/unblinding values.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
An issue was discovered in Arm Mbed TLS before 2.23.0. Because of a side channel in modular exponentiation, an RSA private key used in a secure enclave could be disclosed.
An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
A Lucky 13 timing side channel in mbedtls_ssl_decrypt_buf in library/ssl_msg.c in Trusted Firmware Mbed TLS through 2.23.0 allows an attacker to recover secret key information. This affects CBC mode because of a computed time difference based on a padding length.