CVE-2022-3413 Missing authorization in GitLab

Medium 4.3 Published Updated

Developers and Maintainers can improperly view Audit Events in GitLab EE, exposing sensitive activity logs to unauthorized users.

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

CVE-2022-3413 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 9 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Incorrect authorization during display of Audit Events in GitLab EE affecting all versions from 14.5 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2, allowed Developers to view the project's Audit Events and Developers or Maintainers to view the group's Audit Events. These should have been restricted to Project Maintainers, Group Owners, and above.

Weakness: CWE-639

Which versions are affected by CVE-2022-3413?

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

PackageAffectedFixed in
gitlab BitnamiFrom 14.5.015.3.5, 15.4.4, 15.5.2

Products include Gitlab Gitlab.

How do I fix CVE-2022-3413?

Upgrade gitlab to a fixed version for your release line: 15.3.5, 15.4.4 or 15.5.2.

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

Is CVE-2022-3413 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2022-3413, GHSA-9672-4fh3-mcfg, UBUNTU-CVE-2022-3413.

Is CVE-2022-3413 in your software?

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

Check your SBOMs for free