CVE-2022-2539 Information disclosure in GitLab
A project member can improperly filter issues by contact and organization, leading to unauthorized data disclosure.
- 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-2539?
CVE-2022-2539 is a medium-severity vulnerability in Gitlab Gitlab, published on 5 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.6 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1, allowed a project member to filter issues by contact and organization.
Which versions are affected by CVE-2022-2539?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 14.6.0 | 15.0.5, 15.1.4, 15.2.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-2539?
Upgrade gitlab to a fixed version for your release line: 15.0.5, 15.1.4 or 15.2.1.
Is CVE-2022-2539 being exploited?
There is no known exploitation of CVE-2022-2539 in the wild and no public exploit code.
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-2539, GHSA-238w-mq8v-6c9c, UBUNTU-CVE-2022-2539.