dbcve.org
GitLabApplication

CVE-2022-0751

HIGH · 8.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 →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Inaccurate display of Snippet files containing special characters in all versions of GitLab CE/EE allows an attacker to create Snippets with misleading content which could trick unsuspecting users into executing arbitrary 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

GitLab CE/EE fails to properly render or sanitize special characters in Snippet file content, allowing attackers to craft malicious snippets that visually misrepresent their nature. This display ambiguity could trick users into believing a file is harmless (e.g., a text file) when it actually contains executable commands or malicious content.

MitigationUpgrade GitLab to the patched version; alternatively, disable Snippet creation features until the patch can be applied.

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:>= 10.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version-manifest.txt, or look at the GitLab admin dashboard under Help > Version
    Affected if The installed version falls within any of these ranges: >= 10.0 and < 14.6.5, OR >= 14.7 and < 14.7.4, OR >= 14.8 and < 14.8.2
  2. Confirm Snippets feature is enabled
    Check GitLab configuration in /etc/gitlab/gitlab.rb for 'gitlab_rails["gitlab_snippets_enabled"]' or check via admin area under Settings > General > Visibility and access controls
    Affected if Snippets are enabled (set to true) - the vulnerability only applies when the Snippets feature is active
  3. Verify Snippet file content rendering behavior
    Create a test Snippet containing characters that could be visually ambiguous (e.g., right-to-left override characters, zero-width characters, or extension spoofing) and view how GitLab displays it in the web UI
    Affected if The content renders in a way that could mislead a user about the file's true nature (e.g., showing a .txt extension while containing executable content)

You are affected if your GitLab version is within the affected ranges AND the Snippets feature is enabled, allowing crafted snippets to visually misrepresent their content to users.

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 the patched version; alternatively, disable Snippet creation features until the patch can be applied.

Recommended fix High confidence

14.6.5, 14.7.4, or 14.8.2 (or any later version in the 14.x series)

  1. Identify your current GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin area
  2. Back up your GitLab database and repositories using `gitlab-backup create`
  3. For self-managed installations: Follow the official GitLab upgrade documentation for your installation method (omnibus, source, etc.)
  4. Upgrade to version 14.6.5 or later in the 14.6.x series, OR version 14.7.4 or later, OR version 14.8.2 or later
  5. Verify the upgrade completed successfully by checking GitLab status with `gitlab-rake gitlab:check`
  6. Confirm the new version is running in the admin area under Help > Version
Caveat Review GitLab upgrade guides for any intermediate version requirements between your current version and target version, as some upgrades may require stepping through intermediate releases

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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