{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","type":"apk","namespace":"alpine","name":"mbedtls","version":"3.6.4-r0","qualifiers":{"arch":"loongarch64","distroversion":"edge","reponame":"main"},"subpath":"","is_vulnerable":false,"next_non_vulnerable_version":"3.6.5-r0","latest_non_vulnerable_version":"3.6.6-r0","affected_by_vulnerabilities":[],"fixing_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/97816?format=json","vulnerability_id":"VCID-h19d-wea1-mbcx","summary":"In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_import_public_key does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. Specifically, an out-of-bounds read in mbedtls_lms_import_public_key allows context-dependent attackers to trigger a crash or limited adjacent-memory disclosure by supplying a truncated LMS (Leighton-Micali Signature) public-key buffer under four bytes. An LMS public key starts with a 4-byte type indicator. The function mbedtls_lms_import_public_key reads this type indicator before validating the size of its input.","references":[{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108788","reference_id":"1108788","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108788"},{"reference_url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-4.md","reference_id":"mbedtls-security-advisory-2025-06-4.md","reference_type":"","scores":[{"value":"4.8","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:P/P:M/B:A/M:M/D:T/2025-07-08T13:17:24Z/"}],"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-4.md"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}],"aliases":["CVE-2025-49601"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-h19d-wea1-mbcx"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/104617?format=json","vulnerability_id":"VCID-jh8m-huq1-f7gw","summary":"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.","references":[{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-52496","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-52496"},{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108785","reference_id":"1108785","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108785"},{"reference_url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-1.md","reference_id":"mbedtls-security-advisory-2025-06-1.md","reference_type":"","scores":[{"value":"7.8","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N"},{"value":"Track*","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:P/A:N/T:T/P:M/B:A/M:M/D:R/2025-07-08T14:07:04Z/"}],"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-1.md"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}],"aliases":["CVE-2025-52496"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-jh8m-huq1-f7gw"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/98239?format=json","vulnerability_id":"VCID-q56y-6umw-h3et","summary":"In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.","references":[{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108787","reference_id":"1108787","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108787"},{"reference_url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-3.md","reference_id":"mbedtls-security-advisory-2025-06-3.md","reference_type":"","scores":[{"value":"4.9","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:P/P:M/B:A/M:M/D:T/2025-07-08T13:18:22Z/"}],"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-3.md"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}],"aliases":["CVE-2025-49600"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-q56y-6umw-h3et"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/119744?format=json","vulnerability_id":"VCID-q8z7-t6t1-aqef","summary":"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).","references":[{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47917","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-47917"},{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108791","reference_id":"1108791","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108791"},{"reference_url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-7.md","reference_id":"mbedtls-security-advisory-2025-06-7.md","reference_type":"","scores":[{"value":"8.9","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:T/P:M/B:A/M:M/D:T/2025-07-22T14:22:32Z/"}],"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-7.md"},{"reference_url":"https://mbed-tls.readthedocs.io/en/latest/tech-updates/security-advisories/","reference_id":"security-advisories","reference_type":"","scores":[{"value":"8.9","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:T/P:M/B:A/M:M/D:T/2025-07-22T14:22:32Z/"}],"url":"https://mbed-tls.readthedocs.io/en/latest/tech-updates/security-advisories/"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}],"aliases":["CVE-2025-47917"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-q8z7-t6t1-aqef"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/104772?format=json","vulnerability_id":"VCID-rrnf-p8e2-fyg6","summary":"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.","references":[{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-52497","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-52497"},{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108786","reference_id":"1108786","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108786"},{"reference_url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-2.md","reference_id":"mbedtls-security-advisory-2025-06-2.md","reference_type":"","scores":[{"value":"4.8","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:P/P:M/B:A/M:M/D:T/2025-07-08T13:18:40Z/"}],"url":"https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-2.md"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/144364?format=json","purl":"pkg:apk/alpine/mbedtls@3.6.4-r0?arch=loongarch64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}],"aliases":["CVE-2025-52497"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-rrnf-p8e2-fyg6"}],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/mbedtls@3.6.4-r0%3Farch=loongarch64&distroversion=edge&reponame=main"}