CVE-2024-28960: n/a
An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0, and Mbed Crypto. The PSA Crypto API mishandles shared memory.
AI Analysis
Technical Summary
CVE-2024-28960 identifies a vulnerability in the PSA Crypto API implementation within Mbed TLS (versions 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0) and Mbed Crypto. The root cause is the mishandling of shared memory, which is a critical resource used to exchange data between different components or processes securely. Improper management of this shared memory can lead to unauthorized access or leakage of sensitive cryptographic material, thereby compromising confidentiality. The vulnerability does not require any privileges or user interaction to exploit, and it can be triggered remotely over the network, increasing its risk profile. The CVSS v3.1 score of 8.2 reflects a high severity, primarily due to the high impact on confidentiality (C:H), low impact on integrity (I:L), and no impact on availability (A:N). The weakness is categorized under CWE-284, which relates to improper access control, indicating that the PSA Crypto API fails to enforce adequate restrictions on shared memory usage. Although no exploits have been reported in the wild yet, the vulnerability affects a widely used cryptographic library embedded in many IoT and embedded devices, which are prevalent in industrial, telecommunications, and consumer sectors. The lack of patches linked in the provided data suggests that users should monitor official Mbed TLS and Mbed Crypto repositories for updates and advisories. The vulnerability's exploitation could allow attackers to extract cryptographic keys or sensitive data, undermining the security guarantees of systems relying on these libraries.
Potential Impact
For European organizations, the impact of CVE-2024-28960 is significant, especially for those deploying embedded systems, IoT devices, or industrial control systems that utilize Mbed TLS or Mbed Crypto for cryptographic operations. Confidentiality breaches could lead to exposure of sensitive data, including cryptographic keys, which may facilitate further attacks such as data decryption, impersonation, or unauthorized access to protected resources. Critical infrastructure sectors such as energy, manufacturing, and telecommunications, which increasingly rely on embedded cryptography, are at heightened risk. The vulnerability's remote exploitability without authentication or user interaction increases the attack surface, potentially allowing attackers to compromise devices at scale. This could disrupt supply chains, cause data breaches, or undermine trust in secure communications. Given the widespread use of Mbed TLS in embedded and IoT devices, the scope of affected systems is broad, encompassing devices deployed in both enterprise and operational technology environments across Europe.
Mitigation Recommendations
European organizations should take immediate steps to mitigate CVE-2024-28960 by upgrading affected Mbed TLS versions to 2.28.8 or later and Mbed Crypto to 3.6.0 or later once patches are officially released. Until patches are applied, organizations should audit their use of the PSA Crypto API to identify and restrict any shared memory operations that could be exploited. Employ network segmentation and strict access controls to limit exposure of vulnerable devices to untrusted networks. Implement monitoring for unusual cryptographic API usage patterns or memory access anomalies that could indicate exploitation attempts. For embedded device manufacturers, incorporate secure coding practices to avoid shared memory mishandling and conduct thorough security testing of cryptographic components. Additionally, coordinate with supply chain partners to ensure that firmware and software updates addressing this vulnerability are deployed promptly. Finally, maintain up-to-date inventories of devices using Mbed TLS or Mbed Crypto to prioritize remediation efforts effectively.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Finland
CVE-2024-28960: n/a
Description
An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0, and Mbed Crypto. The PSA Crypto API mishandles shared memory.
AI-Powered Analysis
Technical Analysis
CVE-2024-28960 identifies a vulnerability in the PSA Crypto API implementation within Mbed TLS (versions 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0) and Mbed Crypto. The root cause is the mishandling of shared memory, which is a critical resource used to exchange data between different components or processes securely. Improper management of this shared memory can lead to unauthorized access or leakage of sensitive cryptographic material, thereby compromising confidentiality. The vulnerability does not require any privileges or user interaction to exploit, and it can be triggered remotely over the network, increasing its risk profile. The CVSS v3.1 score of 8.2 reflects a high severity, primarily due to the high impact on confidentiality (C:H), low impact on integrity (I:L), and no impact on availability (A:N). The weakness is categorized under CWE-284, which relates to improper access control, indicating that the PSA Crypto API fails to enforce adequate restrictions on shared memory usage. Although no exploits have been reported in the wild yet, the vulnerability affects a widely used cryptographic library embedded in many IoT and embedded devices, which are prevalent in industrial, telecommunications, and consumer sectors. The lack of patches linked in the provided data suggests that users should monitor official Mbed TLS and Mbed Crypto repositories for updates and advisories. The vulnerability's exploitation could allow attackers to extract cryptographic keys or sensitive data, undermining the security guarantees of systems relying on these libraries.
Potential Impact
For European organizations, the impact of CVE-2024-28960 is significant, especially for those deploying embedded systems, IoT devices, or industrial control systems that utilize Mbed TLS or Mbed Crypto for cryptographic operations. Confidentiality breaches could lead to exposure of sensitive data, including cryptographic keys, which may facilitate further attacks such as data decryption, impersonation, or unauthorized access to protected resources. Critical infrastructure sectors such as energy, manufacturing, and telecommunications, which increasingly rely on embedded cryptography, are at heightened risk. The vulnerability's remote exploitability without authentication or user interaction increases the attack surface, potentially allowing attackers to compromise devices at scale. This could disrupt supply chains, cause data breaches, or undermine trust in secure communications. Given the widespread use of Mbed TLS in embedded and IoT devices, the scope of affected systems is broad, encompassing devices deployed in both enterprise and operational technology environments across Europe.
Mitigation Recommendations
European organizations should take immediate steps to mitigate CVE-2024-28960 by upgrading affected Mbed TLS versions to 2.28.8 or later and Mbed Crypto to 3.6.0 or later once patches are officially released. Until patches are applied, organizations should audit their use of the PSA Crypto API to identify and restrict any shared memory operations that could be exploited. Employ network segmentation and strict access controls to limit exposure of vulnerable devices to untrusted networks. Implement monitoring for unusual cryptographic API usage patterns or memory access anomalies that could indicate exploitation attempts. For embedded device manufacturers, incorporate secure coding practices to avoid shared memory mishandling and conduct thorough security testing of cryptographic components. Additionally, coordinate with supply chain partners to ensure that firmware and software updates addressing this vulnerability are deployed promptly. Finally, maintain up-to-date inventories of devices using Mbed TLS or Mbed Crypto to prioritize remediation efforts effectively.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2024-03-13T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 690a3b69ff58c9332ff0a5cc
Added to database: 11/4/2025, 5:44:09 PM
Last enriched: 11/11/2025, 6:29:03 PM
Last updated: 12/20/2025, 10:46:59 AM
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14298: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in damian-gora FiboSearch – Ajax Search for WooCommerce
MediumCVE-2025-12492: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
MediumCVE-2025-13619: CWE-269 Improper Privilege Management in CMSSuperHeroes Flex Store Users
CriticalCVE-2025-12820: CWE-862 Missing Authorization in Pure WC Variation Swatches
UnknownCVE-2025-14735: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in nestornoe Amazon affiliate lite Plugin
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.