What is the severity of CVE-2023-2069?

CVE-2023-2069 is considered a high severity vulnerability due to the potential leakage of sensitive CI/CD variables.

Which versions of GitLab are affected by CVE-2023-2069?

CVE-2023-2069 affects GitLab versions from 10.0 to before 12.9.8, 12.10 from 12.10.0 to before 12.10.7, and 13.0 before 13.0.1.

How do I fix CVE-2023-2069?

To fix CVE-2023-2069, upgrade GitLab to version 12.9.8 or later, 12.10.7 or later, or 13.0.1 or later.

What is the impact of CVE-2023-2069?

The impact of CVE-2023-2069 allows a developer role user to exploit the import project feature to disclose CI/CD variables.

How was CVE-2023-2069 discovered?

CVE-2023-2069 was discovered through security research and reported by the GitLab community.

Vulnerability/
CVE-2023-2069

medium

6.4

CWE

668

3/5/2023

30/1/2025

CVE-2023-2069

First published: Wed May 03 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 10.0 before 12.9.8, all versions starting from 12.10 before 12.10.7, all versions starting from 13.0 before 13.0.1. A user with the role of developer could use the import project feature to leak CI/CD variables.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.0<12.9.8
GitLab	>=12.10.0<12.10.7
GitLab	>=13.0<13.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-2069?
CVE-2023-2069 is considered a high severity vulnerability due to the potential leakage of sensitive CI/CD variables.
Which versions of GitLab are affected by CVE-2023-2069?
CVE-2023-2069 affects GitLab versions from 10.0 to before 12.9.8, 12.10 from 12.10.0 to before 12.10.7, and 13.0 before 13.0.1.
How do I fix CVE-2023-2069?
To fix CVE-2023-2069, upgrade GitLab to version 12.9.8 or later, 12.10.7 or later, or 13.0.1 or later.
What is the impact of CVE-2023-2069?
The impact of CVE-2023-2069 allows a developer role user to exploit the import project feature to disclose CI/CD variables.
How was CVE-2023-2069 discovered?
CVE-2023-2069 was discovered through security research and reported by the GitLab community.

collector/nvd-latest
agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/10.0
version/gitlab/12.10.0
version/gitlab/13.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-2069?
CVE-2023-2069 is considered a high severity vulnerability due to the potential leakage of sensitive CI/CD variables.
Which versions of GitLab are affected by CVE-2023-2069?
CVE-2023-2069 affects GitLab versions from 10.0 to before 12.9.8, 12.10 from 12.10.0 to before 12.10.7, and 13.0 before 13.0.1.
How do I fix CVE-2023-2069?
To fix CVE-2023-2069, upgrade GitLab to version 12.9.8 or later, 12.10.7 or later, or 13.0.1 or later.
What is the impact of CVE-2023-2069?
The impact of CVE-2023-2069 allows a developer role user to exploit the import project feature to disclose CI/CD variables.
How was CVE-2023-2069 discovered?
CVE-2023-2069 was discovered through security research and reported by the GitLab community.