dbcve.org
GitLabApplication

CVE-2022-1954

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-01
Fix available
A fix is available. Upgrade to 14.10.5 / 15.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Regular Expression Denial of Service vulnerability in GitLab CE/EE affecting all versions from 1.0.2 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker to make a GitLab instance inaccessible via specially crafted web server response headers

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 Regular Expression Denial of Service (ReDoS) vulnerability in GitLab CE/EE allows specially crafted web server response headers to trigger inefficient regex processing, causing excessive CPU consumption that renders the GitLab instance inaccessible.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later to patch the vulnerable regex pattern in header processing.

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:>= 1.0.2, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.0

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
Low

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

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 command: gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file
    Affected if Version is < 14.10.5, OR >= 15.0.0 and < 15.0.4, OR exactly 15.1.0
  2. Verify GitLab web service is running
    Check if unicorn/puma or gitlab-workhorse processes are active: systemctl status gitlab-runsvdir or ps aux | grep gitlab
    Affected if GitLab web interface is accessible (vulnerable regex runs in header processing)
  3. Confirm header processing is enabled
    GitLab processes response headers by default in its web server component. No explicit config check needed - this is default behavior for any running GitLab instance.
    Affected if GitLab is running as a web service (this is the default operational mode)

If GitLab version falls within 14.10.5 > version >= 1.0.2, 15.0.4 > version >= 15.0.0, or version equals 15.1.0, the instance is vulnerable to ReDoS via crafted response headers.

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.10.5 / 15.0.4 or later
Fixed in 14.10.515.0.4
Interim mitigation

Upgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later to patch the vulnerable regex pattern in header processing.

Recommended fix High confidence

14.10.5 (for 14.x) or 15.0.4 (for 15.0.x) or 15.1.1 (for 15.1.x); prefer latest stable 15.x release for best security

  1. 1. Identify the currently installed GitLab version using `gitlab-rake gitlab:env:info` or checking the GitLab admin dashboard
  2. 2. Determine which upgrade path applies based on current version: if on 14.x line upgrade to >=14.10.5, if on 15.0.x upgrade to >=15.0.4, if on 15.1.x upgrade to >=15.1.1
  3. 3. Backup the GitLab database and repositories before upgrading
  4. 4. Follow the official GitLab upgrade documentation for your package manager (Omnibus) or source installation
  5. 5. Run `sudo gitlab-ctl reconfigure` after package installation
  6. 6. Verify GitLab is operational post-upgrade
  7. 7. Test that the application responds normally to confirm the ReDoS vulnerability is mitigated
Caveat Major version upgrades between GitLab major releases may require database migrations and have breaking changes - review release notes before upgrading across major versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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