dbcve.org
GitLabApplication

CVE-2022-2270

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-01
Fix available
A fix is available. Upgrade to 14.10.5 / 15.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab had an authorization flaw where it incorrectly verified permissions when accessing Conan package information, causing package names to be disclosed to unauthorized users. The vulnerability stems from improper access control logic in the package name resolution endpoint.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later. After upgrading, verify that unauthorized users can no longer access Conan package names in private projects.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 12.4.0, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the exact version number
    Affected if The version falls within these ranges: 12.4.0 to 14.10.4, 15.0.0 to 15.0.3, or exactly 15.1.0
  2. Identify Conan package repositories
    Navigate to the project packages area or query the database for packages with package_type='conan'
    Affected if Any project contains Conan packages and the GitLab version is affected
  3. Verify project visibility settings
    Check the visibility level of projects hosting Conan packages under Project Settings > General > Visibility
    Affected if Projects with Conan packages are set to Private and the GitLab version is affected
  4. Test unauthorized access to package names
    As a non-member or guest user without reporter privileges, attempt to access the Conan package name resolution endpoint or view package information in a private project
    Affected if An unauthorized user can view Conan package names in private projects, confirming the authorization bypass

A user is affected if their GitLab version is 12.4.0-14.10.4, 15.0.0-15.0.3, or 15.1.0 AND they have private projects containing Conan packages accessible to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.10.5 / 15.0.4 or later
Fixed in 14.10.515.0.4
Interim mitigation

Upgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later. After upgrading, verify that unauthorized users can no longer access Conan package names in private projects.

Recommended fix High confidence

14.10.5, 15.0.4, or 15.1.1 (depending on your current major/minor version)

  1. Identify your current GitLab version using the GitLab admin dashboard or `gitlab-rake gitlab:env:info`
  2. Review the upgrade path chart at https://docs.gitlab.com/ee/update/#upgrade-paths to plan a safe upgrade sequence
  3. Back up your GitLab database and repositories before upgrading
  4. Upgrade to version 14.10.5 or later (if on 14.x line), OR upgrade to 15.0.4 or later (if on 15.0.x line), OR upgrade to 15.1.1 or later (if on 15.1.x line)
  5. After upgrade, verify that Conan package access permissions are correctly enforced by testing unauthorized access
Caveat Patch upgrades typically have low risk but always review release notes for deprecations; ensure backup before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2270 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data