CVE-2022-2499 Information disclosure in GitLab
An insecure direct object reference in GitLab's Jira integration allows attackers to leak Jira issues.
- 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-2499?
CVE-2022-2499 is a low-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 issue has been discovered in GitLab EE affecting all versions starting from 13.10 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. GitLab's Jira integration has an insecure direct object reference vulnerability that may be exploited by an attacker to leak Jira issues.
Weakness: CWE-639
Which versions are affected by CVE-2022-2499?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.10.0 | 15.0.5, 15.1.4, 15.2.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-2499?
Upgrade gitlab to a fixed version for your release line: 15.0.5, 15.1.4 or 15.2.1.
Is CVE-2022-2499 being exploited?
There is no known exploitation of CVE-2022-2499 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-2499, GHSA-48jv-2rrr-w2f7, UBUNTU-CVE-2022-2499.