OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)
- 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
- 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: yes
- Technical impact: partial
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, the POST /api/v1alpha1/autobuild endpoint in internal/openchoreo-api/api/handlers/webhook_handler.go selected a webhook provider from caller-controlled X-Event-Key, accepted Bitbucket requests without HMAC-SHA256 in X-Hub-Signature or a configured bitbucket-secret, and allowed unauthenticated build triggers for components matched by repository URL and branch, including cross-provider triggers using attacker-supplied commit SHAs. 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: yes · Technical impact: partial
- 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
- 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-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-rc.2