dbcve.org
GitLabApplication

CVE-2022-2229

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 improper authorization issue in GitLab CE/EE affecting all versions from 13.7 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker to extract the value of an unprotected variable they know the name of in public projects or private projects they're a member of.

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 CE/EE versions prior to 14.10.5, 15.0.4, and 15.1.1 contain an improper authorization flaw that allows authenticated users in public projects or members of private projects to extract the values of unprotected variables by knowing their names, bypassing intended access controls.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later to resolve the authorization bypass. Review existing variables in affected projects to confirm no unauthorized access occurred.

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:>= 13.7.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify installed GitLab version
    Run command: `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the version number
    Affected if Version is 13.7.0 through 14.10.4, 15.0.0 through 15.0.3, or exactly 15.1.0
  2. Check for CI/CD variables in projects
    Navigate to Project Settings > CI/CD > Variables in the GitLab web UI, or use API: `GET /projects/:id/variables` with a project token
    Affected if Any project contains CI/CD variables defined (the vulnerable feature)
  3. Identify public projects with variables
    In GitLab, filter projects by Public visibility that have CI/CD variables enabled. Use API: `GET /projects?visibility=public` and check each for variables
    Affected if Public projects exist with CI/CD variables defined
  4. Verify private project membership access
    Review which users have access to private projects containing CI/CD variables. Use API: `GET /projects/:id/members`
    Affected if Private projects with CI/CD variables have members beyond just administrators (any authenticated user with project access can exploit the flaw)

Your environment is affected if the GitLab version falls within the affected ranges AND there are CI/CD variables in any public projects or in private projects where authenticated users have member access.

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 to resolve the authorization bypass. Review existing variables in affected projects to confirm no unauthorized access occurred.

Recommended fix High confidence

15.1.1 or latest 15.1.x stable release (or 15.2+ if available)

  1. 1. Back up your GitLab instance data and configuration
  2. 2. Plan maintenance window as upgrade requires downtime
  3. 3. For GitLab installations using Omnibus: run 'gitlab-ctl stop' to stop services
  4. 4. For package-based installations: download the appropriate package for your OS from GitLab's downloads page
  5. 5. Install the new package (e.g., 'dpkg -i' for Debian/Ubuntu or 'rpm -Uvh' for RHEL/CentOS)
  6. 6. Reconfigure GitLab: run 'gitlab-ctl reconfigure'
  7. 7. Verify the upgrade by checking GitLab version at /help (admin area > Settings > General)
  8. 8. Confirm the running version is 14.10.5, 15.0.4, 15.1.1, or later
Caveat Upgrade may require downtime; review GitLab upgrade path prerequisites and ensure compatible PostgreSQL version before upgrading to 15.x

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2229 — 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-2229 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