dbcve.org
GitLabApplication

CVE-2022-1174

HIGH · 7.5 CVSS v3.1 Published 2022-04-04
Fix available
A fix is available. Upgrade to 14.7.7 / 14.8.5 or later.
See remediation →
84/100
Remediation priority · High
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
A potential DoS vulnerability was discovered in Gitlab CE/EE versions 13.7 before 14.7.7, all versions starting from 14.8 before 14.8.5, all versions starting from 14.9 before 14.9.2 allowed an attacker to trigger high CPU usage via a special crafted input added in Issues, Merge requests, Milestones, Snippets, Wiki pages, etc.

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

A specially crafted input added to Issues, Merge requests, Milestones, Snippets, or Wiki pages in GitLab CE/EE versions prior to 14.7.7, 14.8.5, and 14.9.2 triggers excessive CPU consumption, leading to denial of service.

MitigationUpgrade GitLab to version 14.7.7, 14.8.5, 14.9.2 or later to patch the vulnerability.

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:>= 13.7.0, < 14.7.7>= 14.8.0, < 14.8.5>= 14.9.0, < 14.9.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version. Alternatively, check the version file at `/opt/gitlab/version` or via `gitlab-ctl version`.
    Affected if The installed version falls within any of these ranges: >= 13.7.0 and < 14.7.7, OR >= 14.8.0 and < 14.8.5, OR >= 14.9.0 and < 14.9.2
  2. Verify GitLab web interface is accessible
    Attempt to access the GitLab instance via web browser at the configured hostname or IP address.
    Affected if The GitLab web interface is reachable and the instance is running a vulnerable version from step 1
  3. Confirm public or internal project features are enabled
    Check if Issues, Merge Requests, Milestones, Snippets, or Wiki pages are enabled in any project or group settings. Review project settings under Settings > General or check via GitLab API: `GET /projects/:id` and look for `issues_enabled`, `merge_requests_enabled`, `snippets_enabled`, or `wiki_enabled` fields.
    Affected if Any of these features (Issues, Merge Requests, Milestones, Snippets, or Wiki) are enabled on the instance and the version is vulnerable

If the GitLab version is in the affected ranges AND the web interface is accessible with any of Issues, Merge Requests, Milestones, Snippets, or Wiki features enabled, the environment is vulnerable to CVE-2022-1174.

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.7.7 / 14.8.5 / 14.9.2 or later
Fixed in 14.7.714.8.514.9.2
Interim mitigation

Upgrade GitLab to version 14.7.7, 14.8.5, 14.9.2 or later to patch the vulnerability.

Recommended fix High confidence

14.9.2 or later (or 14.8.5, 14.7.7 depending on your current branch)

  1. 1. Back up your current GitLab instance data and configuration.
  2. 2. Identify your current GitLab version using the command: gitlab-rake gitlab:env:info
  3. 3. For versions 13.7.x through 14.6.x: Upgrade directly to 14.7.7 or later.
  4. 4. For version 14.7.x: Upgrade to 14.7.7 or later.
  5. 5. For version 14.8.x: Upgrade to 14.8.5 or later.
  6. 6. For version 14.9.0-14.9.1: Upgrade to 14.9.2 or later.
  7. 7. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Docker).
  8. 8. After upgrade, verify the instance is running: gitlab-rake gitlab:check
Caveat Patch releases within the same major.minor version typically have minimal breaking changes; however, review GitLab release notes for any noted incompatibilities.

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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