CVE-2024-4024 Authentication Bypass by Assumed-Immutable Data in GitLab

High 7.3 Published Updated

Attackers can take over GitLab accounts linked to other users' Bitbucket accounts when Bitbucket is configured as an OAuth provider.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2024-4024?

CVE-2024-4024 is a high-severity authentication bypass vulnerability in Gitlab Gitlab, published on 25 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-287, CWE-302

Which versions are affected by CVE-2024-4024?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 7.8.016.9.6, 16.10.4, 16.11.1

Products include Gitlab Gitlab.

How do I fix CVE-2024-4024?

Upgrade gitlab to a fixed version for your release line: 16.9.6, 16.10.4 or 16.11.1.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2024-4024 being exploited?

There is no known exploitation of CVE-2024-4024 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2024-4024, GHSA-pvxf-9mm4-92xf, UBUNTU-CVE-2024-4024.

Is CVE-2024-4024 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free