OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation
- 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 1.0.3, 1.1.3, 1.2.0-rc.2, 1.2.0
- 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
OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.3, 1.1.3, and 1.2.0-rc.2, internal/cluster-gateway/server.go exposed /api/proxy/, /api/exec/, and /api/wirelogs/ on an internal listener without requiring a client certificate or token, allowing any network-reachable caller to read tenant Kubernetes Secrets, mutate workloads, and execute commands across connected data planes. This issue is fixed in versions 1.0.3, 1.1.3, and 1.2.0-rc.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- openchoreo openchoreo
fixed in 1.0.3; From 1.1.0 · fixed in 1.1.3; From 1.2.0-rc.1 · fixed in 1.2.0-rc.2
- github.com/openchoreo/openchoreoGo
fixed in 1.0.3; From 1.1.0 · fixed in 1.1.3; From 1.2.0-rc.1 · fixed in 1.2.0
- github.com/openchoreo/openchoreoGo
fixed in 1.0.3
- github.com/openchoreo/openchoreoGo
From 1.1.0 · fixed in 1.1.3
- github.com/openchoreo/openchoreoGo
From 1.2.0-rc.1 · fixed in 1.2.0