What is the severity of CVE-2023-0319?

CVE-2023-0319 has been rated as a high severity vulnerability due to its potential to expose sensitive project environment names.

How do I fix CVE-2023-0319?

To fix CVE-2023-0319, upgrade your GitLab installation to version 15.8.5 or later, or to version 15.9.4 or later, or to version 15.10.1 or later depending on your current version.

Who is affected by CVE-2023-0319?

CVE-2023-0319 affects all GitLab versions starting from 13.6 to 15.8.5, 15.9 to 15.9.4, and 15.10 to 15.10.0.

What does CVE-2023-0319 allow attackers to do?

CVE-2023-0319 allows unauthorized users to read environment names that are supposed to be restricted to project members.

Is a workaround available for CVE-2023-0319?

No official workaround is provided for CVE-2023-0319; upgrading to a non-vulnerable version is the recommended action.

Vulnerability/
CVE-2023-0319

medium

5.8

CWE

863

5/4/2023

2/8/2024

CVE-2023-0319

First published: Wed Apr 05 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 13.6 before 15.8.5, all versions starting from 15.9 before 15.9.4, all versions starting from 15.10 before 15.10.1, allowing to read environment names supposed to be restricted to project memebers only.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.6.0<15.8.5
GitLab	>=13.6.0<15.8.5
GitLab	>=15.9.0<15.9.4
GitLab	>=15.9.0<15.9.4
GitLab	=15.10.0
GitLab	=15.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-0319?
CVE-2023-0319 has been rated as a high severity vulnerability due to its potential to expose sensitive project environment names.
How do I fix CVE-2023-0319?
To fix CVE-2023-0319, upgrade your GitLab installation to version 15.8.5 or later, or to version 15.9.4 or later, or to version 15.10.1 or later depending on your current version.
Who is affected by CVE-2023-0319?
CVE-2023-0319 affects all GitLab versions starting from 13.6 to 15.8.5, 15.9 to 15.9.4, and 15.10 to 15.10.0.
What does CVE-2023-0319 allow attackers to do?
CVE-2023-0319 allows unauthorized users to read environment names that are supposed to be restricted to project members.
Is a workaround available for CVE-2023-0319?
No official workaround is provided for CVE-2023-0319; upgrading to a non-vulnerable version is the recommended action.

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.6.0
version/gitlab/15.9.0
version/gitlab/15.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-2023-0319?
CVE-2023-0319 has been rated as a high severity vulnerability due to its potential to expose sensitive project environment names.
How do I fix CVE-2023-0319?
To fix CVE-2023-0319, upgrade your GitLab installation to version 15.8.5 or later, or to version 15.9.4 or later, or to version 15.10.1 or later depending on your current version.
Who is affected by CVE-2023-0319?
CVE-2023-0319 affects all GitLab versions starting from 13.6 to 15.8.5, 15.9 to 15.9.4, and 15.10 to 15.10.0.
What does CVE-2023-0319 allow attackers to do?
CVE-2023-0319 allows unauthorized users to read environment names that are supposed to be restricted to project members.
Is a workaround available for CVE-2023-0319?
No official workaround is provided for CVE-2023-0319; upgrading to a non-vulnerable version is the recommended action.