What is the severity of CVE-2022-2270?

CVE-2022-2270 has a medium severity rating due to its impact on package name leakage.

How do I fix CVE-2022-2270?

To fix CVE-2022-2270, upgrade to GitLab versions 14.10.5, 15.0.4, or 15.1.1 or later.

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

CVE-2022-2270 affects all GitLab versions from 12.4 before 14.10.5, 15.0 before 15.0.4, and 15.1 before 15.1.1.

What kind of vulnerability is CVE-2022-2270?

CVE-2022-2270 is a permissions verification vulnerability leading to unauthorized exposure of Conan package names.

Who is affected by CVE-2022-2270?

All users of GitLab community and enterprise editions from the specified affected versions are vulnerable to CVE-2022-2270.

Vulnerability/
CVE-2022-2270

medium

5.3

CWE

276

1/7/2022

3/8/2024

CVE-2022-2270

First published: Fri Jul 01 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 12.4 before 14.10.5, all versions starting from 15.0 before 15.0.4, all versions starting from 15.1 before 15.1.1. GitLab was leaking Conan packages names due to incorrect permissions verification.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.4.0<14.10.5
GitLab	>=12.4.0<14.10.5
GitLab	>=15.0.0<15.0.4
GitLab	>=15.0.0<15.0.4
GitLab	=15.1.0
GitLab	=15.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2270?
CVE-2022-2270 has a medium severity rating due to its impact on package name leakage.
How do I fix CVE-2022-2270?
To fix CVE-2022-2270, upgrade to GitLab versions 14.10.5, 15.0.4, or 15.1.1 or later.
What versions of GitLab are affected by CVE-2022-2270?
CVE-2022-2270 affects all GitLab versions from 12.4 before 14.10.5, 15.0 before 15.0.4, and 15.1 before 15.1.1.
What kind of vulnerability is CVE-2022-2270?
CVE-2022-2270 is a permissions verification vulnerability leading to unauthorized exposure of Conan package names.
Who is affected by CVE-2022-2270?
All users of GitLab community and enterprise editions from the specified affected versions are vulnerable to CVE-2022-2270.

agent/type
agent/references
agent/weakness
agent/author
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/12.4.0
version/gitlab/15.0.0
version/gitlab/15.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-2022-2270?
CVE-2022-2270 has a medium severity rating due to its impact on package name leakage.
How do I fix CVE-2022-2270?
To fix CVE-2022-2270, upgrade to GitLab versions 14.10.5, 15.0.4, or 15.1.1 or later.
What versions of GitLab are affected by CVE-2022-2270?
CVE-2022-2270 affects all GitLab versions from 12.4 before 14.10.5, 15.0 before 15.0.4, and 15.1 before 15.1.1.
What kind of vulnerability is CVE-2022-2270?
CVE-2022-2270 is a permissions verification vulnerability leading to unauthorized exposure of Conan package names.
Who is affected by CVE-2022-2270?
All users of GitLab community and enterprise editions from the specified affected versions are vulnerable to CVE-2022-2270.