CVE-2022-3060 Server-side request forgery in GitLab

High 7.3 Published Updated

An authenticated attacker can exploit improper resource control in Error Tracking to force victims into making unintended arbitrary requests.

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

CVE-2022-3060 is a high-severity server-side request forgery vulnerability in Gitlab Gitlab, published on 17 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Improper control of a resource identifier in Error Tracking in GitLab CE/EE affecting all versions from 12.7 allows an authenticated attacker to generate content which could cause a victim to make unintended arbitrary requests

Weakness: CWE-22

Which versions are affected by CVE-2022-3060?

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

PackageAffectedFixed in
gitlab BitnamiFrom 12.7.015.2.5, 15.3.4, 15.4.1

Products include Gitlab Gitlab.

How do I fix CVE-2022-3060?

Upgrade gitlab to a fixed version for your release line: 15.2.5, 15.3.4 or 15.4.1.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2022-3060 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2022-3060, GHSA-g5cm-j62r-w7f5, UBUNTU-CVE-2022-3060.

Is CVE-2022-3060 in your software?

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

Check your SBOMs for free