Gitpod Classic Affected by Bitbucket OAuth Token Exposure via Redirect Fragment

Vulnerability Description

Gitpod is a developer platform for cloud development environments. In versions before main-gha.33628 for both Gitpod Classic and Gitpod Classic Enterprise, OAuth integration with Bitbucket in certain conditions allowed a crafted link to expose a valid Bitbucket access token via the URL fragment when clicked by an authenticated user. This resulted from how Bitbucket returned tokens and how Gitpod handled the redirect flow. The issue was limited to Bitbucket (GitHub and GitLab integrations were not affected), required user interaction, and has been mitigated through redirect handling and OAuth logic hardening. The issue was resolved in main-gha.33628 and later. There are no workarounds.

References

• https://github.com/gitpod-io/gitpod/security/advisories/GHSA-63fw-3jgp-2p2g
• https://github.com/gitpod-io/gitpod/pull/20983
• https://github.com/gitpod-io/gitpod/commit/a736c1b83bd781786af0da705d0acebabfba7862