CVE-2022-1545 Information disclosure in GitLab
Unauthorized project members can disclose confidential note details via the API if tagged, requiring an upgrade to GitLab.
- 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-1545?
CVE-2022-1545 is a medium-severity vulnerability in Gitlab Gitlab, published on 11 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
It was possible to disclose details of confidential notes created via the API in Gitlab CE/EE affecting all versions from 13.2 prior to 14.8.6, 14.9 prior to 14.9.4, and 14.10 prior to 14.10.1 if an unauthorised project member was tagged in the note.
Which versions are affected by CVE-2022-1545?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.2.0 | 14.8.6, 14.9.4, 14.10.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-1545?
Upgrade gitlab to a fixed version for your release line: 14.8.6, 14.9.4 or 14.10.1.
Is CVE-2022-1545 being exploited?
There is no known exploitation of CVE-2022-1545 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-1545, GHSA-mc38-g3j7-hgww.