dbcve.org
GitLabApplication

CVE-2022-3286

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.2.5 / 15.3.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
Lack of IP address checking in GitLab EE affecting all versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows a group member to bypass IP restrictions when using a deploy token

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 fails to enforce IP address restrictions when authenticating with deploy tokens. Group members can bypass configured IP allow-listing by using a deploy token, since the application does not validate the client IP against the defined IP restriction rules for deploy token authentication.

MitigationUpgrade GitLab EE to version 15.2.5, 15.3.4, 15.4.1 or later. Review existing IP restriction policies and deploy token usage 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:>= 14.2, < 15.2.5>= 15.3, < 15.3.4>= 15.4, < 15.4.1

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the exact version number
    Affected if The installed version falls within 14.2 to 15.2.4, 15.3.0 to 15.3.3, or 15.4.0
  2. Confirm IP allowlisting is configured
    Navigate to GitLab admin area > Settings > Network > IP allowlist, or check the gitlab.yml configuration file for defined IP restriction rules
    Affected if IP addresses or CIDR ranges are listed in the allowlist configuration
  3. Determine if deploy tokens exist
    Check GitLab under Settings > Repository > Deploy tokens, or use the API endpoint `GET /deploy_tokens` with administrative access
    Affected if One or more deploy tokens are active in the instance
  4. Verify deploy token usage logs
    Review GitLab audit logs under Admin Area > Monitoring > Audit Events, filtering for event types related to deploy token authentication
    Affected if Deploy token authentication events are present in logs from IP addresses outside the configured allowlist

A user is affected if their GitLab version is in the vulnerable range AND they have both IP allowlisting configured AND active 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.2.5 / 15.3.4 / 15.4.1 or later
Fixed in 15.2.515.3.415.4.1
Interim mitigation

Upgrade GitLab EE to version 15.2.5, 15.3.4, 15.4.1 or later. Review existing IP restriction policies and deploy token usage to confirm no unauthorized access occurred.

Recommended fix High confidence

15.4.1 (or 15.3.4 or 15.2.5 depending on your current major version branch)

  1. 1. Identify your current GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the Admin Area > Dashboard
  2. 2. Determine which upgrade path applies: if running 14.2 to <15.2, upgrade to 15.2.5; if running 15.3.x, upgrade to 15.3.4; if running 15.4.x, upgrade to 15.4.1
  3. 3. Back up your GitLab instance data before upgrading
  4. 4. Update your GitLab installation using your package manager (e.g., `sudo apt-get update && sudo apt-get install gitlab-ce` or `sudo yum update gitlab-ce`)
  5. 5. After upgrade, verify the version with `sudo gitlab-rake gitlab:env:info`
  6. 6. Confirm IP address restrictions are now properly enforced for deploy tokens in Admin Area > Settings > Network > IP restrictions
Caveat Review GitLab release notes for your target version for any behavior changes; standard upgrade precautions apply

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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