dbcve.org
GitLabApplication

CVE-2022-2501

HIGH · 7.5 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 15.0.5 / 15.1.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 access control issue in GitLab EE affecting all versions from 12.0 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 allows an attacker to bypass IP allow-listing and download artifacts. This attack only bypasses IP allow-listing, proper permissions are still required.

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 EE has an improper access control vulnerability in all versions from 12.0 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 that allows attackers to bypass IP allow-listing protections when downloading artifacts. While proper permissions are still required for artifact access, the IP restriction bypass enables attacks from unauthorized IP addresses.

MitigationUpgrade GitLab EE to version 15.0.5, 15.1.4, 15.2.1 or later to patch the IP allow-listing bypass vulnerability.

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, < 15.0.5>= 15.1.0, < 15.1.4= 15.2

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. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version-manifest.json` to obtain the exact GitLab version number
    Affected if The installed version falls within 12.0.0 to 15.0.4, 15.1.0 to 15.1.3, or exactly 15.2.0 (including 15.2.0 before 15.2.1)
  2. Verify IP allowlisting is configured
    Check GitLab admin settings under Settings > Network > IP Allowlist, or inspect `/etc/gitlab/gitlab.rb` for `gitlab_rails['ip_whitelist']` entries
    Affected if IP allowlisting rules are defined in GitLab and the GitLab instance version is vulnerable
  3. Confirm artifact download functionality is accessible
    Check if any projects contain CI/CD artifacts by navigating to a project's CI/CD > Artifacts section, or query the API endpoint `/api/v4/projects/:id/artifacts`
    Affected if Any project has CI/CD artifacts stored and the IP allowlisting feature is meant to restrict access to them

You are affected if your GitLab version is 12.0.x through 15.0.4, 15.1.x through 15.1.3, or exactly 15.2.0, AND you have IP allowlisting configured to protect artifact downloads.

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 15.0.5 / 15.1.4 or later
Fixed in 15.0.515.1.4
Interim mitigation

Upgrade GitLab EE to version 15.0.5, 15.1.4, 15.2.1 or later to patch the IP allow-listing bypass vulnerability.

Recommended fix High confidence

15.0.5, 15.1.4, 15.2.1, or later (preferably latest stable 15.x release)

  1. 1. Back up your GitLab instance including database, repositories, and configuration files
  2. 2. Review the current GitLab version by running `sudo gitlab-rake gitlab:env:info`
  3. 3. Determine the appropriate upgrade path based on your current version (GitLab recommends upgrading one minor version at a time for major version jumps)
  4. 4. Update the GitLab package repository: `sudo apt-get update` for Debian/Ubuntu or `sudo yum check-update` for RHEL/CentOS
  5. 5. Install the updated GitLab package: `sudo apt-get install gitlab-ee` or `sudo yum install gitlab-ee`
  6. 6. Reconfigure GitLab: `sudo gitlab-ctl reconfigure`
  7. 7. Verify the upgrade was successful: `sudo gitlab-rake gitlab:env:info` and check the version matches 15.0.5, 15.1.4, 15.2.1, or newer
  8. 8. Test that artifact downloads work correctly with IP allow-listing enforced
Caveat Major version upgrades may require additional migration time and could have breaking changes; review GitLab release notes before upgrading across multiple minor versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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