CVE-2022-1193 Information disclosure in GitLab
Attackers can view latest commit details in private projects via Merge Requests, exposing sensitive code information.
- 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-1193?
CVE-2022-1193 is a medium-severity vulnerability in Gitlab Gitlab, published on 11 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Improper access control in GitLab CE/EE versions 10.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allows a malicious actor to obtain details of the latest commit in a private project via Merge Requests under certain circumstances
Weakness: CWE-863
Which versions are affected by CVE-2022-1193?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 10.7.0 | 14.7.7, 14.8.5, 14.9.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-1193?
Upgrade gitlab to a fixed version for your release line: 14.7.7, 14.8.5 or 14.9.2.
Is CVE-2022-1193 being exploited?
There is no known exploitation of CVE-2022-1193 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-1193, GHSA-p4cp-frqx-5q69, UBUNTU-CVE-2022-1193.