Security readout for executives and security teams
Plain-English summary
GitLab could let a person with their own Bitbucket credentials take over someone else's GitLab account, but only when Bitbucket OAuth is used and the victim account is linked to Bitbucket. The business risk is account compromise with access to repositories, issues, secrets, and CI/CD functions available to that GitLab user.
Executive priority
Treat this as high priority where GitLab uses Bitbucket OAuth because compromise can lead to source code and CI/CD access. Patch affected instances promptly, then review linked-account and login activity. Lower urgency is reasonable only when Bitbucket OAuth is not enabled.
Technical view
The issue is an authentication bypass by assumed-immutable data (CWE-302) in GitLab CE/EE. Affected ranges are 7.8 before 16.9.6, 16.10 before 16.10.4, and 16.11 before 16.11.1. The attack path requires Bitbucket as a GitLab OAuth 2.0 provider, Bitbucket credentials, and user interaction.
Likely exposure
Exposure is most likely in self-managed GitLab CE/EE instances that enabled Bitbucket OAuth 2.0 and have GitLab accounts linked to Bitbucket identities. Instances not using Bitbucket as an OAuth provider are not indicated as exposed by the supplied sources.
Exploitation context
The CVE is not listed as KEV in the bundle, and no cited source confirms active exploitation. Public details state account takeover may be possible under certain conditions, but the provided evidence does not define those conditions fully.
Researcher notes
The main uncertainty is the phrase “under certain conditions”; the supplied sources do not provide full triggering detail. The CVSS vector indicates network access, low attack complexity, low privileges, required user interaction, and high confidentiality and integrity impact, with no availability impact stated.
Mitigation direction
- Upgrade GitLab to 16.9.6, 16.10.4, 16.11.1, or later as applicable.
- Check GitLab vendor guidance and the linked issue for any additional advisories.
- Review whether Bitbucket OAuth 2.0 is enabled and still required.
- Temporarily disable Bitbucket OAuth if business impact is acceptable until patched.
- Notify GitLab administrators to prioritize account-integrity review after patching.
Validation and detection
- Inventory GitLab CE/EE versions and compare them to the affected ranges.
- Confirm whether Bitbucket is configured as an OAuth 2.0 provider.
- Identify accounts linked to Bitbucket identities for targeted review.
- Review authentication logs for unusual Bitbucket OAuth sign-ins or account-linking activity.
- Verify the deployed GitLab version is at or above the fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-302: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-4024 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N2.15.2GitLabVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #452426CVE reference, GitLab · issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Assumed-Immutable Data
Authentication Bypass by Assumed-Immutable Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.