What is the severity of CVE-2024-2191?

CVE-2024-2191 has been classified with a high severity due to its potential exposure of sensitive information.

How do I fix CVE-2024-2191?

To resolve CVE-2024-2191, upgrade GitLab to version 16.11.5 or 17.0.3 or higher.

Who is affected by CVE-2024-2191?

CVE-2024-2191 affects all versions of GitLab CE and EE starting from 16.9 to prior 16.11.5, 17.0 to prior 17.0.3, and 17.1 to prior 17.1.1.

What does CVE-2024-2191 exploit?

CVE-2024-2191 allows merge request titles to be publicly visible despite being configured for project members only.

When was CVE-2024-2191 discovered?

CVE-2024-2191 was discovered recently, affecting specific versions of GitLab released in 2023.

Vulnerability/
CVE-2024-2191

medium

5.3

CWE

284

26/6/2024

17/9/2024

CVE-2024-2191: Improper Access Control in GitLab

First published: Wed Jun 26 2024(Updated: )

An issue was discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows merge request title to be visible publicly despite being set as project members only.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.9.0<16.11.5
GitLab	>=16.9.0<16.11.5
GitLab	>=17.0.0<17.0.3
GitLab	>=17.0.0<17.0.3
GitLab	=17.1.0
GitLab	=17.1.0

Remedy

Upgrade to versions 17.1.1, 17.0.3, 16.11.5 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-2191?
CVE-2024-2191 has been classified with a high severity due to its potential exposure of sensitive information.
How do I fix CVE-2024-2191?
To resolve CVE-2024-2191, upgrade GitLab to version 16.11.5 or 17.0.3 or higher.
Who is affected by CVE-2024-2191?
CVE-2024-2191 affects all versions of GitLab CE and EE starting from 16.9 to prior 16.11.5, 17.0 to prior 17.0.3, and 17.1 to prior 17.1.1.
What does CVE-2024-2191 exploit?
CVE-2024-2191 allows merge request titles to be publicly visible despite being configured for project members only.
When was CVE-2024-2191 discovered?
CVE-2024-2191 was discovered recently, affecting specific versions of GitLab released in 2023.

agent/weakness
agent/references
agent/type
agent/remedy
agent/description
agent/first-publish-date
agent/title
agent/severity
agent/author
agent/event
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/16.9.0
version/gitlab/17.0.0
version/gitlab/17.1.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-2024-2191?
CVE-2024-2191 has been classified with a high severity due to its potential exposure of sensitive information.
How do I fix CVE-2024-2191?
To resolve CVE-2024-2191, upgrade GitLab to version 16.11.5 or 17.0.3 or higher.
Who is affected by CVE-2024-2191?
CVE-2024-2191 affects all versions of GitLab CE and EE starting from 16.9 to prior 16.11.5, 17.0 to prior 17.0.3, and 17.1 to prior 17.1.1.
What does CVE-2024-2191 exploit?
CVE-2024-2191 allows merge request titles to be publicly visible despite being configured for project members only.
When was CVE-2024-2191 discovered?
CVE-2024-2191 was discovered recently, affecting specific versions of GitLab released in 2023.