Search for packages
| purl | pkg:deb/debian/mbedtls@2.28.3-1 |
| Next non-vulnerable version | None. |
| Latest non-vulnerable version | None. |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-4sbv-dqyv-6baw
Aliases: CVE-2024-45157 |
An issue was discovered in Mbed TLS before 2.28.9 and 3.x before 3.6.1, in which the user-selected algorithm is not used. Unlike previously documented, enabling MBEDTLS_PSA_HMAC_DRBG_MD_TYPE does not cause the PSA subsystem to use HMAC_DRBG: it uses HMAC_DRBG only when MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG and MBEDTLS_CTR_DRBG_C are disabled. | There are no reported fixed by versions. |
|
VCID-5bxk-rknm-zfhc
Aliases: CVE-2024-23775 |
Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could lead to information disclosure or denial of service. |
Affected by 1 other vulnerability. |
|
VCID-7ppw-f9jy-k7ae
Aliases: CVE-2025-52497 |
Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input. |
Affected by 1 other vulnerability. |
|
VCID-7v3a-5q44-cucz
Aliases: CVE-2025-48965 |
Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero. |
Affected by 1 other vulnerability. |
|
VCID-98cg-wuhp-qudq
Aliases: CVE-2025-47917 |
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN). |
Affected by 1 other vulnerability. |
|
VCID-f1fz-b8b6-dfb8
Aliases: CVE-2024-23170 |
Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could lead to information disclosure or denial of service. |
Affected by 1 other vulnerability. |
|
VCID-gvkn-6e2m-dyez
Aliases: CVE-2025-27809 |
Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname. |
Affected by 1 other vulnerability. |
|
VCID-kchn-2wez-bbb2
Aliases: CVE-2025-27810 |
Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication bypasses such as replays. |
Affected by 1 other vulnerability. |
|
VCID-pj6w-rufw-nqgd
Aliases: CVE-2025-54764 |
Mbed TLS before 3.6.5 allows a local timing attack against certain RSA operations, and direct calls to mbedtls_mpi_mod_inv or mbedtls_mpi_gcd. |
Affected by 1 other vulnerability. |
|
VCID-vp4q-81cq-33cw
Aliases: CVE-2025-59438 |
Mbed TLS through 3.6.4 has an Observable Timing Discrepancy. |
Affected by 1 other vulnerability. |
|
VCID-vs6q-c4ug-xfer
Aliases: CVE-2024-28755 |
An issue was discovered in Mbed TLS 3.5.x before 3.6.0. When an SSL context was reset with the mbedtls_ssl_session_reset() API, the maximum TLS version to be negotiated was not restored to the configured one. An attacker was able to prevent an Mbed TLS server from establishing any TLS 1.3 connection, potentially resulting in a Denial of Service or forced version downgrade from TLS 1.3 to TLS 1.2. |
Affected by 1 other vulnerability. |
|
VCID-wsvw-6tmk-3kdj
Aliases: CVE-2024-28960 |
mbedtls: Insecure handling of shared memory in PSA Crypto APIs |
Affected by 1 other vulnerability. |
|
VCID-zpq1-dwvf-8ka2
Aliases: CVE-2025-52496 |
Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery. |
Affected by 1 other vulnerability. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1teg-yvuy-4kga | Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could lead to information disclosure or denial of service. |
CVE-2022-46392
|
| VCID-5x2e-paq2-nyf9 | Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could result in arbitrary code execution. |
CVE-2021-44732
|
| VCID-7ppw-f9jy-k7ae | Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input. |
CVE-2025-52497
|
| VCID-7v3a-5q44-cucz | Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero. |
CVE-2025-48965
|
| VCID-8vmc-tp28-wyae | In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX. |
CVE-2021-24119
|
| VCID-98cg-wuhp-qudq | Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN). |
CVE-2025-47917
|
| VCID-k8w1-nrjy-wfbe | Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could result in arbitrary code execution. |
CVE-2022-35409
|
| VCID-t2j5-4x1d-2kb1 | Use of a Broken or Risky Cryptographic Algorithm in the function mbedtls_mpi_exp_mod() in lignum.c in Mbed TLS Mbed TLS all versions before 3.0.0, 2.27.0 or 2.16.11 allows attackers with access to precise enough timing and memory access information (typically an untrusted operating system attacking a secure enclave such as SGX or the TrustZone secure world) to recover the private keys used in RSA. |
CVE-2021-36647
|
| VCID-x5we-9dmz-p7bh | Multiple vulnerabilities have been discovered in Mbed TLS, the worst of which could result in arbitrary code execution. |
CVE-2021-43666
|
| VCID-zpq1-dwvf-8ka2 | Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery. |
CVE-2025-52496
|