CVE-2023-2190 Authorization Bypass Through User-Controlled Key in GitLab

Medium 6.5 Published Updated

Attackers can view new commits to private projects via forks created when the project was public, exposing sensitive code changes.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2023-2190?

CVE-2023-2190 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.10 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1. It may be possible for users to view new commits to private projects in a fork created while the project was public.

Weakness: CWE-639

Which versions are affected by CVE-2023-2190?

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

PackageAffectedFixed in
gitlab BitnamiFrom 13.10.015.11.10, 16.0.6, 16.1.1

Products include Gitlab Gitlab.

How do I fix CVE-2023-2190?

Upgrade gitlab to a fixed version for your release line: 15.11.10, 16.0.6 or 16.1.1.

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

Is CVE-2023-2190 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2190 exists.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2023-2190, GHSA-258v-vrh7-jgj2, UBUNTU-CVE-2023-2190.

Is CVE-2023-2190 in your software?

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

Check your SBOMs for free