dbcve.org
GitLabApplication

CVE-2022-0154

HIGH · 8.0 CVSS v3.1 Published 2022-01-18
Fix available
A fix is available. Upgrade to 14.4.5 / 14.5.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 7.7 before 14.4.5, all versions starting from 14.5.0 before 14.5.3, all versions starting from 14.6.0 before 14.6.2. GitLab was vulnerable to a Cross-Site Request Forgery attack that allows a malicious user to have their GitHub project imported on another GitLab user account.

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 versions 7.7 through 14.6.2 contain a Cross-Site Request Forgery (CSRF) vulnerability in the GitHub import functionality. The flaw allows an attacker to trick an authenticated GitLab user into importing the attacker's GitHub project into the victim's GitLab account by exploiting missing or improper anti-CSRF token validation on the import endpoint.

MitigationUpgrade to GitLab versions 14.4.5, 14.5.3, 14.6.2 or later. As an interim measure, disable GitHub import functionality or implement CSRF protection at the WAF level until patching is possible.

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:>= 7.7, < 14.4.5>= 14.5.0, < 14.5.3>= 14.6.0, < 14.6.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 the GitLab admin panel under Help > Version to find the exact version number
    Affected if Version falls within any of these ranges: >= 7.7 and < 14.4.5, OR >= 14.5.0 and < 14.5.3, OR >= 14.6.0 and < 14.6.2
  2. Verify GitHub import is enabled
    Check GitLab admin settings under Settings > Imports > GitHub import or review the gitlab.yml configuration file for import_sources setting
    Affected if GitHub import is enabled in the GitLab instance
  3. Confirm import endpoint accessibility
    Attempt to access the /import/github endpoint (GET request) or review routing configuration for github_import API routes
    Affected if The GitHub import endpoint is accessible and responds without CSRF token errors when accessed directly

A user is affected if their GitLab version is within the vulnerable ranges AND the GitHub import feature is enabled, allowing potential CSRF-based import of malicious repositories into victim accounts.

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.4.5 / 14.5.3 / 14.6.2 or later
Fixed in 14.4.514.5.314.6.2
Interim mitigation

Upgrade to GitLab versions 14.4.5, 14.5.3, 14.6.2 or later. As an interim measure, disable GitHub import functionality or implement CSRF protection at the WAF level until patching is possible.

Recommended fix High confidence

14.6.2 or later (latest stable 14.x release)

  1. Identify your current GitLab version by checking the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. Plan for upgrade: backup your GitLab database and configuration, and schedule a maintenance window
  3. Upgrade GitLab to version 14.6.2 or later (recommended: latest stable 14.x release)
  4. For omnibus installations, follow the standard upgrade path using `apt-get update && apt-get install gitlab-ce` or `yum install gitlab-ce`
  5. For installations from source, follow the GitLab upgrade guides for your specific version path
  6. After upgrade, verify GitLab is running correctly and test the import functionality to confirm the fix
Caveat Major version upgrades (e.g., 14.x to 15.x) may require additional migration steps and could have compatibility impacts; review GitLab upgrade guides for any breaking changes between your current version and target version

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
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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