🛡️ openSUSE-SU-2024:0037-1 — mbedtls (CVE-2024-23170)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for mbedtls

This update for mbedtls fixes the following issues:

  • Update to version 2.28.7:
  • Resolves CVE-2024-23170 boo#1219336
  • Update to 2.28.6:

Changes:

  • Mbed TLS is now released under a dual Apache-2.0 OR GPL-2.0-or-later

license. Users may choose which license they take the code under.

  • Update to 2.28.5:

Features:

  • The documentation of mbedtls_ecp_group now describes the optimized

representation of A for some curves. Fixes gh#Mbed-TLS/mbedtls#8045.

Security:

  • Developers using mbedtls_pkcs5_pbes2() or mbedtls_pkcs12_pbe() should

review the size of the output buffer passed to this function, and note that

the output after decryption may include CBC padding. Consider moving to the

new functions mbedtls_pkcs5_pbes2_ext() or mbedtls_pkcs12_pbe_ext() which

checks for overflow of the output buffer and reports the actual length of

the output.

  • Improve padding calculations in CBC decryption, NIST key unwrapping and

RSA OAEP decryption. With the previous implementation, some compilers

(notably recent versions of Clang and IAR) could produce non-constant time

code, which could allow a padding oracle attack if the attacker has access

to precise timing measurements.

  • Fix a buffer overread when parsing short TLS application data records in

ARC4 or null-cipher cipher suites. Credit to OSS-Fuzz.

Bugfix:

  • Fix x509 certificate generation to conform to RFC 5480 / RFC 5758 when

using ECC key. The certificate was rejected by some crypto frameworks.

Fixes gh#Mbed-TLS/mbedtls#2924.

  • Fix some cases where mbedtls_mpi_mod_exp, RSA key construction or ECDSA

signature can silently return an incorrect result in low memory conditions.

  • Fix IAR compiler warnings. Fixes gh#Mbed-TLS/mbedtls#7873,

gh#Mbed-TLS/mbedtls#4300.

  • Fix an issue when parsing an otherName subject alternative name into a

mbedtls_x509_san_other_name struct. The type-id of the otherName was not

copied to the struct. This meant that the struct had incomplete information

about the otherName SAN and contained uninitialized memory.

  • Fix the detection of HardwareModuleName otherName SANs. These were being

detected by comparing the wrong field and the check was erroneously

inverted.

  • Fix an error when MBEDTLS_ECDSA_SIGN_ALT is defined but not

MBEDTLS_ECDSA_VERIFY_ALT, causing ecdsa verify to fail. Fixes

gh#Mbed-TLS/mbedtls#7498. Functions in the ssl_cache module now return a

negative MBEDTLS_ERR_xxx error code on failure. Before, they returned 1 to

indicate failure in some cases involving a missing entry or a full cache.

Changes:

  • In configurations with ARIA or Camellia but not AES, the value of

MBEDTLS_CIPHER_BLKSIZE_MAX was 8, rather than 16 as the name might suggest.

This did not affect any library code, because this macro was only used in

relation with CMAC which does not support these ciphers. Its value is now

16 if ARIA or Camellia are present. This may affect application code that

uses this macro.

  • Update to 2.28.4:

Features:

  • Allow MBEDTLS_CONFIG_FILE and MBEDTLS_USER_CONFIG_FILE to be set by

setting the CMake variable of the same name at configuration time.

Bugfix:

  • Fix crypt_and_hash decryption fail when used with a stream cipher

mode of operation, due to the input not being a multiple of the block

size. Resolves #7417.

  • Fix a bug where mbedtls_x509_string_to_names() would return success

when given a invalid name string, if it did not contain '=' or ','.

  • Fix missing PSA initialization in sample programs when

MBEDTLS_USE_PSA_CRYPTO is enabled.

  • Fix clang and armclang compilation error when targeting certain Arm

M-class CPUs (Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23,

SecurCore SC000). Fixes #1077.

  • Fixed an issue that caused compile errors when using CMake and the IAR

toolchain.

  • Fix the build with MBEDTLS_PSA_INJECT_ENTROPY. Fixes #7516.
  • Fix builds on Windows with clang.
  • Fix compilation warnings in aes.c for certain combinations

of configuration options.

  • Fix a compilation error on some platforms when including mbedtls/ssl.h

with all TLS support disabled. Fixes #6628.

Changes:

  • Update test data to avoid failures of unit tests after 2023-08-07, and

update expiring certififcates in the certs

  • Update to 2.28.3:

Features:

  • Use HOSTCC (if it is set) when compiling C code during generation of the

configuration-independent files. This allows them to be generated when CC

is set for cross compilation.

  • AES-NI is now supported with Visual Studio.
  • AES-NI is now supported in 32-bit builds, or when MBEDTLS_HAVE_ASM is

disabled, when compiling with GCC or Clang or a compatible compiler for a

target CPU that supports the requisite instructions (for example gcc -m32

-msse2 -maes -mpclmul). (Generic x86 builds with GCC-like compilers still

r

Affected software

openSUSE-SU-2024:0037-1 is recorded against 1 package.

  • mbedtls (fixed in 2.28.7-bp155.2.3.1)

Timeline and source

Published on 31 January 2024 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

lists.opensuse.org (Advisory)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-01-31
Updated 2026-08-20
Modified 2026-02-04
Fix URL N/A

Affected Packages

Software From version Fixed in
mbedtls 2.28.7-bp155.2.3.1

Free Vulnerability Check

Is your site affected by openSUSE-SU-2024:0037-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2024:0037-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.