Search
Search Results (4 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-52497 | 2 Arm, Mbed | 2 Mbed Tls, Mbedtls | 2025-11-03 | 4.8 Medium |
| 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-52496 | 2 Arm, Mbed | 2 Mbed Tls, Mbedtls | 2025-11-03 | 7.8 High |
| 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-48965 | 2 Arm, Mbed | 2 Mbed Tls, Mbedtls | 2025-11-03 | 4 Medium |
| 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-47917 | 2 Arm, Mbed | 2 Mbed Tls, Mbedtls | 2025-11-03 | 8.9 High |
| 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). | ||||
Page 1 of 1.