StatefulSet and ControllerRevision write permissions allow cross-namespace pod creation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The software affected is Kubernetes, specifically the StatefulSet controller. A user with write access to StatefulSet and ControllerRevision objects in their own namespace could abuse this flaw to create pods in other namespaces, with control over those pods' metadata and specification.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A confused deputy attack exists in the StatefulSet controller that allows a user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects to create a cross-namespace pod. An attacker exploiting this vulnerability would have full control over the resulting pod’s metadata and specification, including namespace selection. Note that the cross-namespace pod will be immediately deleted by the garbage collector unless the attacker is able to construct a valid StatefulSet OwnerReference. This would require referencing the UID of an existing StatefulSet in the victim’s namespace.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Kubernetes Kubernetes
From v1.34.0 · through v1.34.11; From v1.35.0 · through v1.35.8; From v1.36.0 · through v1.36.4; From v1.37.0 · through v1.37.0