CVE intelligence and bounded remediation
CVE-2024-4024 — Gitlab Gitlab security vulnerability
An issue has been discovered in GitLab CE/EE affecting all versions starting from 7.8 before 16.9.6, all versions starting from 16.10 before 16.10.4, all versions starting from 16.11 before 16.11.1. Under certain conditions, an attacker with their Bitbucket account credentials may be able to take over a GitLab account linked to another user's Bitbucket account, if Bitbucket is used as an OAuth 2.0 provider on GitLab.
- Severity
- High
- CVSS
- 8.8 (3.1)
- Published
- 2024-04-25
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-302, CWE-287
Affected products
- gitlab / gitlab
- gitlab / gitlab / 16.11.0
Matched remediation archetype
Authentication bypass and missing authentication
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
- Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
- Review session, token, credential, and proxy trust configuration without attempting account takeover.
Remediate safely
- Apply the supported fix and centralize fail-closed authentication before protected request handling.
- Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
- Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.