dbcve.org
GitLabApplication

CVE-2022-2228

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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
Information exposure in GitLab EE affecting all versions from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker with the appropriate access tokens to obtain CI variables in a group with using IP-based access restrictions even if the GitLab Runner is calling from outside the allowed IP range

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

In GitLab EE, IP-based access restrictions on CI variables can be bypassed. An attacker with valid access tokens can retrieve CI variables from groups protected by IP allowlisting, even when the request originates from an IP outside the permitted range.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later. Review and rotate any potentially exposed CI variables and access tokens as a precaution.

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.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed GitLab version
    Run `gitlab-ctl version` or check the Admin Area > Version (the version number is displayed on the dashboard)
    Affected if The version is 12.0.0 or higher but lower than 14.10.5, OR 15.0.0 or higher but lower than 15.0.4, OR exactly 15.1.0
  2. Confirm the GitLab edition is Enterprise Edition (EE)
    Check the Admin Area > Version page; the edition is listed as 'GitLab Enterprise Edition' (this vulnerability only affects EE, not CE)
    Affected if Running GitLab Enterprise Edition and the version falls in the affected ranges from step 1
  3. Verify if IP-based access restrictions are configured on CI variables
    Navigate to a group Settings > CI/CD > Variables, or Admin Area > Instance-level CI/CD settings, and check for any IP allowlist or IP restriction configuration under variable protection settings
    Affected if IP allowlisting or IP restrictions are enabled on any CI variable protection settings

A user is affected if running a vulnerable GitLab EE version (12.0.0 to 14.10.4, 15.0.0 to 15.0.3, or 15.1.0) AND IP-based restrictions are configured on CI variables or group settings.

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. Review and rotate any potentially exposed CI variables and access tokens as a precaution.

Recommended fix High confidence

14.10.5+ for 14.x users, 15.0.4+ for 15.0.x users, 15.1.1+ for 15.1.0 users

  1. 1. Identify the currently installed GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area.
  2. 2. Determine which upgrade path applies based on your current version: if on 14.x, upgrade to 14.10.5 or later; if on 15.0.x, upgrade to 15.0.4 or later; if on 15.1.0, upgrade to 15.1.1 or later.
  3. 3. Back up your GitLab database and repositories before upgrading.
  4. 4. Stop GitLab services with `sudo gitlab-ctl stop`.
  5. 5. Update GitLab using your package manager: for Debian/Ubuntu run `sudo apt-get update && sudo apt-get install gitlab-ee`; for RHEL/CentOS run `sudo yum install gitlab-ee`.
  6. 6. Reconfigure GitLab with `sudo gitlab-ctl reconfigure`.
  7. 7. Start GitLab services with `sudo gitlab-ctl start`.
  8. 8. Verify the upgrade was successful and check that GitLab is functioning normally.
Caveat Major version upgrades (e.g., 14.x to 15.x) may require additional migration steps and have breaking changes; review GitLab release notes before upgrading across major versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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