VulnerabilityPublished 12 Sep 2023Updated 30 Oct 2025

CVE-2023-29332: Microsoft Azure Kubernetes Service · Weak Randomness

Affects Microsoft Azure Kubernetes ServiceSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.6% chance of exploitation in 30 days – higher than 85% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Sep 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Microsoft Azure Kubernetes Service	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2023-29332, European organizations should: 1) Monitor Microsoft Azure advisories closely and apply security patches or updates to AKS as soon as they become available, prioritizing upgrades from version 1.0. 2) Implement strict network segmentation and access controls to limit exposure of AKS management interfaces and API endpoints. 3) Enforce the principle of least privilege for all identities and service accounts interacting with AKS clusters. 4) Enable and review detailed logging and monitoring of AKS cluster activities to detect anomalous behavior indicative of privilege escalation attempts. 5) Use Azure Security Center and other cloud-native security tools to continuously assess the security posture of AKS deployments. 6) Conduct regular security assessments and penetration testing focused on Kubernetes environments to identify and remediate weaknesses proactively. 7) Educate DevOps and security teams about the risks associated with insufficient randomness and privilege escalation vulnerabilities in cloud orchestration platforms.

Description

Microsoft Azure Kubernetes Service Elevation of Privilege Vulnerability

Impact

For European organizations, the impact of CVE-2023-29332 could be substantial, especially for those leveraging Microsoft Azure Kubernetes Service for container orchestration and cloud-native application deployment. The elevation of privilege vulnerability could allow attackers to gain unauthorized access to sensitive workloads, data, or management functions within AKS clusters. This could lead to data breaches, exposure of confidential information, or unauthorized manipulation of cloud resources. Given the critical role of Kubernetes in modern IT infrastructure, exploitation could disrupt business operations or compromise compliance with data protection regulations such as GDPR. The vulnerability's network-based attack vector and lack of required privileges increase the risk of widespread exploitation if left unmitigated. Organizations in sectors such as finance, healthcare, and critical infrastructure that rely heavily on Azure cloud services may face increased risk of targeted attacks leveraging this flaw.

CWE-330Use of Insufficiently Random Values (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
Implementation
Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
Architecture and Design · Requirements · Libraries or Frameworks
Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Signature Spoofing by Key Recreation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Brute Force (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2023-29332 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2025, 19:26 UTC

WeaknessesCWE-330

Technical details

References

Community reviews

Related threats