Apache Camel K: Camel K Cross-Namespace Build Deputy Attack
- 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
- Fix
- Fixed in 2.8.1, 2.9.2, 2.10.1
- 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
(Externally Controlled Reference to a Resource in Another Sphere), (Authorization Bypass Through User-Controlled Key) vulnerability in Apache Camel K. Authorized users in a Kubernetes namespace can create a Build resource, controlling the Pod generation in a namespace of their choice, including the operator namespace. This issue affects Apache Camel K: from 2.0.0 before 2.8.1, from 2.9.0 before 2.9.2, from 2.10.0 before 2.10.1. Users are recommended to upgrade to version 2.10.1 (or 2.8.1 or 2.9.2), which fixes the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- apache/camel-k
From 2.0.0 · fixed in 2.8.1; From 2.9.0 · fixed in 2.9.2; From 2.10.0 · fixed in 2.10.1
- github.com/apache/camel-kGo
All versions
- github.com/apache/camel-k/v2Go
fixed in 2.8.1; From 2.9.0 · fixed in 2.9.2; From 2.10.0 · fixed in 2.10.1
- github.com/apache/camel-k/v2Go
fixed in 2.8.1
- github.com/apache/camel-k/v2Go
From 2.9.0 · fixed in 2.9.2
- github.com/apache/camel-k/v2Go
From 2.10.0 · fixed in 2.10.1