dbcve.org
GitLabApplication

CVE-2022-0735

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-28
Fix available
A fix is available. Upgrade to 14.6.5 / 14.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions starting from 14.7 before 14.7.4, all versions starting from 14.8 before 14.8.2. An unauthorised user was able to steal runner registration tokens through an information disclosure vulnerability using quick actions commands.

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

An information disclosure vulnerability in GitLab's quick actions feature allowed unauthorized users to extract runner registration tokens. The quick actions command processing improperly handled sensitive data, enabling any user to access tokens that could then be used to register malicious runners in projects.

MitigationUpgrade GitLab to version 14.6.5, 14.7.4, 14.8.2 or later. Review existing runners for unauthorized registrations and rotate any potentially compromised tokens.

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, < 14.6.5>= 14.7, < 14.7.4>= 14.8, < 14.8.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check installed GitLab version
    Access the GitLab admin area or run `sudo gitlab-rake gitlab:env:info` to display the currently installed GitLab version. Compare this version number against the affected ranges: 12.0 through 14.6.4, 14.7.0 through 14.7.3, and 14.8.0 through 14.8.1.
    Affected if The installed version falls within any of the affected ranges (>= 12.0, < 14.6.5 OR >= 14.7, < 14.7.4 OR >= 14.8, < 14.8.2)
  2. Review runner registrations for unauthorized entries
    Navigate to the admin area or project settings > CI/CD > Runners. Inspect the list of registered runners for any runners that were not intentionally registered by an administrator. Look for unknown or unexpected runner names, descriptions, or IP addresses.
    Affected if Any runner exists that was not explicitly registered by a known administrator
  3. Examine audit logs for quick action usage
    In the GitLab admin panel, go to the Audit Logs section. Search for entries involving quick actions, particularly commands that may have accessed project or CI/CD settings. Look for unusual or unauthorized quick action executions.
    Affected if Audit logs show quick action executions by users who should not have had access to runner registration tokens
  4. Check for runner token leakage
    Search project repositories, wiki pages, snippets, and comments for strings matching runner registration token patterns (typically long alphanumeric strings). Also check CI/CD pipeline logs for any exposure of tokens.
    Affected if Any runner registration token is found exposed in project content, logs, or comments
  5. Analyze runner activity for suspicious behavior
    Review recent CI/CD pipeline executions and runner job logs. Look for jobs run by unknown runners, unusual job behaviors, or pipelines accessing resources outside normal activity.
    Affected if Recent CI/CD activity shows jobs executed by runners that were not created by known administrators

A user is affected if their GitLab version falls within the affected ranges AND either unauthorized runners exist in their environment, or runner registration tokens have been exposed through the quick actions vulnerability.

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.6.5 / 14.7.4 / 14.8.2 or later
Fixed in 14.6.514.7.414.8.2
Interim mitigation

Upgrade GitLab to version 14.6.5, 14.7.4, 14.8.2 or later. Review existing runners for unauthorized registrations and rotate any potentially compromised tokens.

Recommended fix High confidence

14.6.5, 14.7.4, 14.8.2, or later (preferably latest 14.x stable)

  1. Back up your GitLab instance data before proceeding
  2. Plan a maintenance window for the upgrade
  3. Review GitLab upgrade documentation for your deployment method (Omnibus, source, etc.)
  4. For Omnibus installations: sudo gitlab-ctl tail-upgrade OR follow the upgrade guide for your package manager
  5. Ensure you upgrade to version 14.6.5, 14.7.4, 14.8.2 or later
  6. After upgrade, verify the instance is functioning correctly
  7. Review audit logs for any suspicious activity using quick actions that may indicate exploitation

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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