CVE-2022-3482 Missing authorization in GitLab
Unauthorized users can view restricted release names in GitLab, exposing sensitive project information to non-members.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-3482?
CVE-2022-3482 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An improper access control issue in GitLab CE/EE affecting all versions from 11.3 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allowed an unauthorized user to see release names even when releases we set to be restricted to project members only
Weakness: CWE-862
Which versions are affected by CVE-2022-3482?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 11.3.0 | 15.4.6, 15.5.5, 15.6.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-3482?
Upgrade gitlab to a fixed version for your release line: 15.4.6, 15.5.5 or 15.6.1.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-3482 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3482 exists.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2022-3482, GHSA-qhh9-23rj-2x83, UBUNTU-CVE-2022-3482.