dbcve.org
GitLabApplication

CVE-2022-1185

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
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 denial of service vulnerability when rendering RDoc files in GitLab CE/EE versions 10 to 14.7.7, 14.8.0 to 14.8.5, and 14.9.0 to 14.9.2 allows an attacker to crash the GitLab web application with a maliciously crafted RDoc file

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 · moderate confidence

A denial of service vulnerability in GitLab CE/EE allows remote attackers to crash the web application by uploading a maliciously crafted RDoc file. The vulnerability exists in the RDoc rendering component across versions 10 through 14.9.2, where specially crafted documentation files trigger a crash condition.

MitigationUpgrade GitLab to version 14.7.8, 14.8.6, 14.9.3, or later. If immediate upgrade is not possible, disable or restrict the RDoc rendering feature and file upload capabilities as a compensating control.

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.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or access the admin panel at /admin/about to view the GitLab version number
    Affected if The displayed version falls within these ranges: >= 10.0.0 and < 14.7.7, OR >= 14.8.0 and < 14.8.5, OR >= 14.9.0 and < 14.9.2
  2. Identify RDoc upload exposure
    Review whether public or authenticated users can upload files to GitLab repositories, wikis, or snippets where RDoc documentation files could be submitted
    Affected if File upload features are accessible to users and RDoc files can be processed by the rendering component
  3. Verify RDoc rendering is active
    Check if the GitLab instance processes or renders RDoc files in any project documentation, wiki pages, or repository readme files
    Affected if RDoc file rendering is enabled and the feature processes uploaded documentation files

You are affected if your GitLab version is 10.0.0 through 14.7.6, 14.8.0 through 14.8.4, or 14.9.0 through 14.9.1, and users can upload or trigger rendering of malicious RDoc files.

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.8, 14.8.6, 14.9.3, or later. If immediate upgrade is not possible, disable or restrict the RDoc rendering feature and file upload capabilities as a compensating control.

Recommended fix High confidence

Upgrade to GitLab 14.9.2 or later (recommended: latest 14.x stable release)

  1. 1. Back up your GitLab database and repository data before upgrading.
  2. 2. Review the GitLab upgrade documentation for your current version at docs.gitlab.com/ee/update/
  3. 3. For package-based installations (Omnibus), update your GitLab package repository and install the new version using: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise).
  4. 4. For source installations, stop GitLab services, download the new version from gitlab.com/gitlab-org/gitlab-ce, and follow the upgrade instructions.
  5. 5. After upgrade, verify GitLab is running: sudo gitlab-ctl status
  6. 6. Test that the web interface is accessible and the application is functioning normally.
  7. 7. If using a proxy or load balancer, ensure connections are properly routed to the upgraded instance.
Caveat Review GitLab release notes for any configuration changes required between your current version and target version; major version jumps may require additional migration steps

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 / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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