CVE-2024-29990
Published: 09 April 2024
Summary
CVE-2024-29990 is a critical-severity Improper Access Control (CWE-284) vulnerability in Microsoft Azure Kubernetes Service Confidential Containers. Its CVSS base score is 9.0 (Critical).
Operationally, ranked in the top 7.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Microsoft Azure Kubernetes Service Confidential Containers is affected by CVE-2024-29990, an elevation-of-privilege vulnerability assigned CWE-284. The flaw carries a CVSS 3.1 score of 9.0 with a network attack vector, high attack complexity, no required privileges or user interaction, and changed scope that yields high impact to confidentiality, integrity, and availability.
An unauthenticated remote attacker can exploit the issue to obtain elevated privileges within the confidential-container environment, potentially allowing full control over container workloads and associated cluster resources.
Microsoft has published remediation guidance in its Security Response Center update guide at the referenced URLs, directing administrators to apply the fixes or configuration changes described there. The associated EPSS score has remained flat at 0.0881 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-26962
Vulnerability details
Microsoft Azure Kubernetes Service Confidential Container Elevation of Privilege 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.
The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.
Device lock enforces restricted access until re-authentication, directly reducing unauthorized use of active sessions.
Supervision and review of access control activities directly detects and remediates improper access configurations or usages.
Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.
By automatically labeling outputs with security attributes, the control supports attribute-based enforcement and reduces exploitability of improper access control weaknesses.
Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.
Requiring prior authorization for each remote access type prevents improper access control over remote connections.
Requiring authorization of wireless access before allowing connections enforces proper access control for this access method.