CVE-2024-5258 Authorization Bypass Through User-Controlled Key in GitLab

Medium 4.4 Published Updated

An authenticated attacker can bypass pipeline authorization logic in GitLab by using a crafted naming convention, potentially accessing restricted resources.

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-5258?

CVE-2024-5258 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 23 May 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 authorization vulnerability exists within GitLab from versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1 where an authenticated attacker could utilize a crafted naming convention to bypass pipeline authorization logic.

Weakness: CWE-863, CWE-639

Which versions are affected by CVE-2024-5258?

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

PackageAffectedFixed in
gitlab BitnamiFrom 16.10.016.10.6, 16.11.3, 17.0.1

Products include Gitlab Gitlab.

How do I fix CVE-2024-5258?

Upgrade gitlab to a fixed version for your release line: 16.10.6, 16.11.3 or 17.0.1.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2024-5258 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2024-5258, GHSA-w2rm-x498-v7f9, UBUNTU-CVE-2024-5258.

Is CVE-2024-5258 in your software?

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

Check your SBOMs for free