CVE-2024-21403 json
Microsoft Azure Kubernetes Service Confidential Container Elevation of Privilege Vulnerability
published 2y ago modified 3mo ago also EUVD-2024-19113
- cvss
- 9.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Microsoft Azure Kubernetes Service Confidential Container Elevation of Privilege Vulnerability
Patch / fix
- Microsoft Azure Kubernetes Service 0.3.3
Is CVE-2024-21403 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
1.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C |
| CNA | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Microsoft Azure Kubernetes Service
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-21403
vendor-advisory, patch
Sources
- CVE List CVE-2024-21403
- NVD CVE-2024-21403
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.