What is the severity of CVE-2022-1545?

CVE-2022-1545 has been classified with a medium severity due to potential unauthorized access to confidential notes.

How do I fix CVE-2022-1545?

To fix CVE-2022-1545, upgrade your GitLab CE/EE installation to version 14.8.6 or later, or 14.9.4 or later.

Which versions are affected by CVE-2022-1545?

CVE-2022-1545 affects GitLab versions from 13.2 to before 14.8.6, 14.9 to before 14.9.4, and 14.10 to before 14.10.1.

What type of vulnerability is CVE-2022-1545?

CVE-2022-1545 is a vulnerability that allows the disclosure of confidential notes created via the GitLab API by unauthorized users.

Who can be impacted by CVE-2022-1545?

Users with unauthorized project access in GitLab can be impacted by CVE-2022-1545 due to its potential for information leakage.

Vulnerability/
CVE-2022-1545

medium

4.3

11/5/2022

3/8/2024

CVE-2022-1545

First published: Wed May 11 2022(Updated: )

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.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.2.0<14.8.6
GitLab	>=13.2.0<14.8.6
GitLab	>=14.9.0<14.9.4
GitLab	>=14.9.0<14.9.4
GitLab	=14.10.0
GitLab	=14.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1545?
CVE-2022-1545 has been classified with a medium severity due to potential unauthorized access to confidential notes.
How do I fix CVE-2022-1545?
To fix CVE-2022-1545, upgrade your GitLab CE/EE installation to version 14.8.6 or later, or 14.9.4 or later.
Which versions are affected by CVE-2022-1545?
CVE-2022-1545 affects GitLab versions from 13.2 to before 14.8.6, 14.9 to before 14.9.4, and 14.10 to before 14.10.1.
What type of vulnerability is CVE-2022-1545?
CVE-2022-1545 is a vulnerability that allows the disclosure of confidential notes created via the GitLab API by unauthorized users.
Who can be impacted by CVE-2022-1545?
Users with unauthorized project access in GitLab can be impacted by CVE-2022-1545 due to its potential for information leakage.

agent/references
agent/author
agent/type
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/13.2.0
version/gitlab/14.9.0
version/gitlab/14.10.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-1545?
CVE-2022-1545 has been classified with a medium severity due to potential unauthorized access to confidential notes.
How do I fix CVE-2022-1545?
To fix CVE-2022-1545, upgrade your GitLab CE/EE installation to version 14.8.6 or later, or 14.9.4 or later.
Which versions are affected by CVE-2022-1545?
CVE-2022-1545 affects GitLab versions from 13.2 to before 14.8.6, 14.9 to before 14.9.4, and 14.10 to before 14.10.1.
What type of vulnerability is CVE-2022-1545?
CVE-2022-1545 is a vulnerability that allows the disclosure of confidential notes created via the GitLab API by unauthorized users.
Who can be impacted by CVE-2022-1545?
Users with unauthorized project access in GitLab can be impacted by CVE-2022-1545 due to its potential for information leakage.