CVE-2022-1157 Information disclosure in GitLab
Attackers can view sensitive data in logs due to missing sanitization of exception messages in GitLab.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-1157?
CVE-2022-1157 is a low-severity vulnerability in Gitlab Gitlab, published on 11 Apr 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
Missing sanitization of logged exception messages in all versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 of GitLab CE/EE causes potential sensitive values in invalid URLs to be logged
Weakness: CWE-532
Which versions are affected by CVE-2022-1157?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | All versions | 14.7.7, 14.8.5, 14.9.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-1157?
Upgrade gitlab to a fixed version for your release line: 14.7.7, 14.8.5 or 14.9.2.
Is CVE-2022-1157 being exploited?
There is no known exploitation of CVE-2022-1157 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-1157, GHSA-cxfq-987j-wpfw, UBUNTU-CVE-2022-1157.