dbcve.org
GitLabApplication

CVE-2022-2533

HIGH · 7.4 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.1.6 / 15.2.4 or later.
See remediation →
83/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 issue has been discovered in GitLab affecting all versions starting from 12.10 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2. GitLab was not performing correct authentication with some Package Registries when IP address restrictions were configured, allowing an attacker already in possession of a valid Deploy Token to misuse it from any location.

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 authentication bypass in Package Registries where IP address restrictions were not properly enforced. When IP restrictions were configured on Package Registries, a valid Deploy Token could be used from any IP address, bypassing the intended IP allowlist security control.

MitigationUpgrade GitLab to version 15.1.6, 15.2.4, 15.3.2 or later. Review deployed tokens for suspicious usage and audit Package Registry access logs for any unauthorized IP addresses.

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.10, < 15.1.6>= 15.2, < 15.2.4>= 15.3, < 15.3.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Check GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the installed version number
    Affected if The installed version falls within >= 12.10, < 15.1.6; >= 15.2, < 15.2.4; or >= 15.3, < 15.3.2
  2. Verify Package Registry is enabled
    Navigate to Admin Area > Packages and Registries > Settings, or check via API: `GET /api/v4/application/settings` looking for `package_registry_enabled`
    Affected if Package Registry is enabled and in use
  3. Confirm IP restrictions are configured for Package Registries
    Check Package Registry settings in Admin Area > Packages and Registries > IP Restrictions, or inspect the GitLab database table `application_settings` for `package_registry_ip_restriction_enabled` or related fields
    Affected if IP restrictions are configured or enabled on Package Registry
  4. Identify active Deploy Tokens
    Review Deploy Tokens in Admin Area > Tokens, or query API: `GET /api/v4/deploy_tokens` to list any active deploy tokens that have access to Package Registry
    Affected if Deploy Tokens exist and are active for Package Registry access

You are affected if your GitLab version is in the vulnerable range AND Package Registry is enabled with IP restrictions configured AND you have Deploy Tokens in use.

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.1.6 / 15.2.4 / 15.3.2 or later
Fixed in 15.1.615.2.415.3.2
Interim mitigation

Upgrade GitLab to version 15.1.6, 15.2.4, 15.3.2 or later. Review deployed tokens for suspicious usage and audit Package Registry access logs for any unauthorized IP addresses.

Recommended fix High confidence

15.1.6, 15.2.4, or 15.3.2 depending on your current minor version

  1. 1. Identify your current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. 2. Determine which upgrade path applies based on your current version: for 12.10-15.1.x upgrade to 15.1.6; for 15.2.x upgrade to 15.2.4; for 15.3-15.3.x upgrade to 15.3.2
  3. 3. Create a full backup of your GitLab instance using `gitlab-backup create`
  4. 4. Stop GitLab services with `gitlab-ctl stop`
  5. 5. Update GitLab using your package manager (e.g., `apt-get update && apt-get install gitlab-ce` or `yum update gitlab-ce`)
  6. 6. Reconfigure GitLab with `gitlab-ctl reconfigure`
  7. 7. Start GitLab services with `gitlab-ctl start`
  8. 8. Verify the upgrade was successful by checking the version at /help in the GitLab UI or running `gitlab-rake gitlab:env:info`
Caveat Minor version upgrades within the same major.minor typically have no breaking changes; however, review GitLab release notes for any deprecation notices

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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