What is the severity of CVE-2022-2512?

The severity of CVE-2022-2512 is considered to be moderate, as it allows former project members to see changes in confidential notes.

How do I fix CVE-2022-2512?

To fix CVE-2022-2512, update your GitLab installation to version 15.0.5, 15.1.4, or 15.2.1 or later.

What versions of GitLab are affected by CVE-2022-2512?

CVE-2022-2512 affects GitLab CE/EE versions from 15.0.0 to 15.0.4, from 15.1.0 to 15.1.3, and exactly 15.2.

What kind of issue is CVE-2022-2512?

CVE-2022-2512 is a vulnerability that fails to enforce proper access control for membership changes in confidential notes.

Can a former member of a GitLab project access confidential notes due to CVE-2022-2512?

Yes, due to CVE-2022-2512, a former project member may still see changes in the TODO list for confidential notes.

Vulnerability/
CVE-2022-2512

medium

6.5

5/8/2022

3/8/2024

CVE-2022-2512

First published: Fri Aug 05 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.0 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. Membership changes are not reflected in TODO for confidential notes, allowing a former project members to read updates via TODOs.

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

Affected Software	Affected Version	How to fix
GitLab	>=15.0.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2
GitLab	>=15.0.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2512?
The severity of CVE-2022-2512 is considered to be moderate, as it allows former project members to see changes in confidential notes.
How do I fix CVE-2022-2512?
To fix CVE-2022-2512, update your GitLab installation to version 15.0.5, 15.1.4, or 15.2.1 or later.
What versions of GitLab are affected by CVE-2022-2512?
CVE-2022-2512 affects GitLab CE/EE versions from 15.0.0 to 15.0.4, from 15.1.0 to 15.1.3, and exactly 15.2.
What kind of issue is CVE-2022-2512?
CVE-2022-2512 is a vulnerability that fails to enforce proper access control for membership changes in confidential notes.
Can a former member of a GitLab project access confidential notes due to CVE-2022-2512?
Yes, due to CVE-2022-2512, a former project member may still see changes in the TODO list for confidential notes.

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

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-2512?
The severity of CVE-2022-2512 is considered to be moderate, as it allows former project members to see changes in confidential notes.
How do I fix CVE-2022-2512?
To fix CVE-2022-2512, update your GitLab installation to version 15.0.5, 15.1.4, or 15.2.1 or later.
What versions of GitLab are affected by CVE-2022-2512?
CVE-2022-2512 affects GitLab CE/EE versions from 15.0.0 to 15.0.4, from 15.1.0 to 15.1.3, and exactly 15.2.
What kind of issue is CVE-2022-2512?
CVE-2022-2512 is a vulnerability that fails to enforce proper access control for membership changes in confidential notes.
Can a former member of a GitLab project access confidential notes due to CVE-2022-2512?
Yes, due to CVE-2022-2512, a former project member may still see changes in the TODO list for confidential notes.