CVE-2022-2095 Information disclosure in GitLab

Medium 4.3 Published Updated

An authenticated user can view public fingerprints and names of deploy keys with write permissions on public projects, exposing sensitive metadata.

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-2022-2095?

CVE-2022-2095 is a medium-severity vulnerability in Gitlab Gitlab, published on 5 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An improper access control check in GitLab CE/EE affecting all versions starting from 13.7 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1 allows a malicious authenticated user to view a public project's Deploy Key's public fingerprint and name when that key has write permission. Note that GitLab never asks for nor stores the private key.

Weakness: CWE-863

Which versions are affected by CVE-2022-2095?

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

PackageAffectedFixed in
gitlab BitnamiFrom 13.7.015.0.5, 15.1.4, 15.2.1

Products include Gitlab Gitlab.

How do I fix CVE-2022-2095?

Upgrade gitlab to a fixed version for your release line: 15.0.5, 15.1.4 or 15.2.1.

Is CVE-2022-2095 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2022-2095, GHSA-hjx6-96hg-jf7x, UBUNTU-CVE-2022-2095.

Is CVE-2022-2095 in your software?

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

Check your SBOMs for free