CVE-2024-35252
Published: 11 June 2024
Summary
CVE-2024-35252 is a high-severity Use of Unmaintained Third Party Components (CWE-1104) vulnerability in Microsoft Azure Storage Data Movement Library. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 9.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
The vulnerability CVE-2024-35252 is a denial of service issue in the Azure Storage Movement Client Library, assigned a CVSS 3.1 base score of 7.5 under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H and associated with CWE-1104.
An unauthenticated remote attacker can trigger the flaw over the network to produce a high-impact loss of availability in affected components, with no user interaction or credentials required.
Microsoft has published an advisory describing the issue and any available mitigations at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-35252. The associated EPSS score has remained flat at a low value of 0.054 with no material rise after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-1893
Vulnerability details
Azure Storage Movement Client Library Denial of Service Vulnerability
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security groups frequently discuss maintenance status of third-party components, aiding identification and avoidance of unmaintained ones.
Maintaining an accurate, reviewed inventory of all system components enables tracking of third-party software versions and maintenance status, reducing the risk of using unmaintained components.
The maintenance policy requires regular updates and upkeep of systems and third-party components, directly reducing the presence of unmaintained software that attackers can exploit.
Requiring quick access to maintenance support and spare parts after failure necessitates using actively supported components rather than unmaintained third-party ones.
Contact with security communities directly informs personnel of unmaintained components and their vulnerabilities, reducing the likelihood of their continued use.
Threat intelligence sharing directly informs organizations of newly discovered vulnerabilities and exploitation in third-party components, enabling timely updates or replacement before attackers can leverage them.
Resource allocation in investment requests funds regular maintenance, patching, and updates of third-party components.
Organization-wide SCRM policy includes ongoing evaluation of third-party component support lifecycles to avoid unmaintained dependencies.