What is the severity of CVE-2023-0805?

The severity of CVE-2023-0805 is categorized as high due to the potential for unauthorized access to sensitive project data.

How do I fix CVE-2023-0805?

To fix CVE-2023-0805, upgrade GitLab EE to version 15.9.6, 15.10.5, or 15.11.1 or later.

Who is affected by CVE-2023-0805?

CVE-2023-0805 affects all GitLab EE versions from 15.2 to earlier than 15.9.6, 15.10 to earlier than 15.10.5, and 15.11 to earlier than 15.11.1.

What impact does CVE-2023-0805 have on GitLab?

CVE-2023-0805 allows a malicious group member to maintain access to public projects even after leaving the group.

Is there a workaround for CVE-2023-0805?

Currently, there are no recommended workarounds for CVE-2023-0805 other than applying the necessary updates.

Vulnerability/
CVE-2023-0805

high

8.1

3/5/2023

2/8/2024

CVE-2023-0805

First published: Wed May 03 2023(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 15.2 before 15.9.6, all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. A malicious group member may continue to have access to the public projects of a public group even after being banned from the public group by the owner.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.2<15.9.6
GitLab	>=15.10<15.10.5
GitLab	>=15.11<15.11.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-0805?
The severity of CVE-2023-0805 is categorized as high due to the potential for unauthorized access to sensitive project data.
How do I fix CVE-2023-0805?
To fix CVE-2023-0805, upgrade GitLab EE to version 15.9.6, 15.10.5, or 15.11.1 or later.
Who is affected by CVE-2023-0805?
CVE-2023-0805 affects all GitLab EE versions from 15.2 to earlier than 15.9.6, 15.10 to earlier than 15.10.5, and 15.11 to earlier than 15.11.1.
What impact does CVE-2023-0805 have on GitLab?
CVE-2023-0805 allows a malicious group member to maintain access to public projects even after leaving the group.
Is there a workaround for CVE-2023-0805?
Currently, there are no recommended workarounds for CVE-2023-0805 other than applying the necessary updates.

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

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-2023-0805?
The severity of CVE-2023-0805 is categorized as high due to the potential for unauthorized access to sensitive project data.
How do I fix CVE-2023-0805?
To fix CVE-2023-0805, upgrade GitLab EE to version 15.9.6, 15.10.5, or 15.11.1 or later.
Who is affected by CVE-2023-0805?
CVE-2023-0805 affects all GitLab EE versions from 15.2 to earlier than 15.9.6, 15.10 to earlier than 15.10.5, and 15.11 to earlier than 15.11.1.
What impact does CVE-2023-0805 have on GitLab?
CVE-2023-0805 allows a malicious group member to maintain access to public projects even after leaving the group.
Is there a workaround for CVE-2023-0805?
Currently, there are no recommended workarounds for CVE-2023-0805 other than applying the necessary updates.