dbcve.org
GitLabApplication

CVE-2022-2992

CRITICAL · 9.9 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 →
100/100
Remediation priority · Urgent
High EPSS Public exploit 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
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated user to achieve remote code execution via the Import from GitHub API endpoint.

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
How this class of weakness works · CWE-74

Untrusted input crosses into a downstream interpreter — SQL, a shell, an HTML page, an LDAP query — without being kept separate from the commands around it, so the attacker's data is read as instructions. This is the parent class behind SQL injection, cross-site scripting, and command injection alike. The durable fix is the same everywhere: keep data and code apart at every boundary, using parameterisation or context-aware encoding rather than building interpreted strings by concatenation.

General guidance for the injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 11.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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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
Recommended fix High confidence

Upgrade to GitLab 15.3.2 or later (15.1.6 for 15.1.x branch, 15.2.4 for 15.2.x branch, 15.3.2 for 15.3.x branch). Recommended: upgrade to the latest stable 15.3.x release or newer.

  1. 1. Back up your GitLab database and repositories before starting the upgrade process
  2. 2. Ensure you have adequate downtime window as GitLab upgrades may require service interruption
  3. 3. For Debian/Ubuntu: Edit /etc/apt/sources.list.d/gitlab_gitlab-ce.list or use the official GitLab APT repository, then run: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise Edition)
  4. 4. For RHEL/CentOS: Edit /etc/yum.repos.d/gitlab_gitlab-ce.repo or use the official GitLab YUM repository, then run: sudo yum install gitlab-ce (or gitlab-ee for Enterprise Edition)
  5. 5. Alternatively, for Omnibus installations: download the appropriate package from GitLab's official downloads page for your OS and install via dpkg or rpm
  6. 6. Run sudo gitlab-ctl reconfigure after installation to apply configuration
  7. 7. Verify the upgrade was successful by checking GitLab version at /help or via gitlab-rake gitlab:env:info
  8. 8. Test that the GitHub import functionality works correctly after upgrade
Caveat GitLab major version upgrades may have breaking changes; review the Changelog for any migration requirements or deprecated features before upgrading across major versions (e.g., 14.x to 15.x).

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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