OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)
openchoreo
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openchoreo/openchoreo Go |
|
|
openchoreo
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openchoreo/openchoreo Go |
|
|
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.
From the CVE record · GitHub_M
The POST /api/v1alpha1/autobuild endpoint selects a webhook provider from the caller-controlled X-Event-Key header and accepts Bitbucket requests without an HMAC-SHA256 signature or configured bitbucket-secret. An unauthenticated caller can trigger builds for components matched by repository URL and branch, including cross-provider triggers with attacker-supplied commit SHAs.
Teams running github.com/openchoreo/openchoreo versions before 1.0.3, from 1.1.0 to before 1.1.3, or from 1.2.0-rc.1 to before 1.2.0-rc.2 should check their deployments.