CVE-2023-5226 Improper Control of Generation of Code ('Code Injection') in GitLab

Medium 4.8 Published Updated

Attackers can bypass branch protection rules to manipulate repository content via crafted branch names, requiring GitLab upgrades.

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-2023-5226?

CVE-2023-5226 is a medium-severity code injection vulnerability in Gitlab Gitlab, published on 1 Dec 2023. 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 affecting all versions before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. Under certain circumstances, a malicious actor bypass prohibited branch checks using a specially crafted branch name to manipulate repository content in the UI.

Weakness: CWE-94

Which versions are affected by CVE-2023-5226?

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

PackageAffectedFixed in
gitlab BitnamiAll versions16.4.3, 16.5.3, 16.6.1

Products include Gitlab Gitlab.

How do I fix CVE-2023-5226?

Upgrade gitlab to a fixed version for your release line: 16.4.3, 16.5.3 or 16.6.1.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2023-5226 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2023-5226, GHSA-6wgj-fxqf-wxj2, UBUNTU-CVE-2023-5226.

Is CVE-2023-5226 in your software?

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

Check your SBOMs for free