GitLabApplication

CVE-2022-3818

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-10
Fix available
A fix is available. Upgrade to 15.3.5 / 15.4.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
An uncontrolled resource consumption issue when parsing URLs in GitLab CE/EE affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to cause performance issues and potentially a denial of service on the GitLab instance.

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 contains an uncontrolled resource consumption vulnerability in its URL parsing functionality. Attackers can craft malicious URLs that cause excessive resource consumption during parsing, leading to performance degradation and potential denial of service on the GitLab instance.

MitigationUpgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later to resolve the URL parsing resource consumption issue.

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:< 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.5.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
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. Determine installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version on the GitLab server. Alternatively, visit the GitLab admin area Help page which displays the version number.
    Affected if The displayed version falls into any of these ranges: < 15.3.5, >= 15.4.0 but < 15.4.4, or >= 15.5.0 but < 15.5.2
  2. Confirm GitLab web service is active
    Check that the GitLab web interface (Puma or Unicorn process) is running. Run 'gitlab-ctl status' or check that port 80/443 is listening.
    Affected if GitLab is actively serving web requests, as URL parsing occurs during normal HTTP request processing
  3. Verify instance is network accessible
    Confirm the GitLab instance has network listeners. Check open ports with 'netstat -tlnp | grep -E "(80|443|8080)"' or review firewall rules.
    Affected if The GitLab instance accepts external or internal HTTP connections, making it reachable for malicious URL requests

If the installed GitLab version is below 15.3.5, between 15.4.0-15.4.3, or between 15.5.0-15.5.1, and the web service is running and network-accessible, the instance is vulnerable to resource exhaustion from crafted URLs.

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 15.3.5 / 15.4.4 / 15.5.2 or later
Fixed in 15.3.515.4.415.5.2
Interim mitigation

Upgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later to resolve the URL parsing resource consumption issue.

Recommended fix High confidence

15.5.2 (or latest stable 15.x release)

  1. Backup your GitLab instance data and configuration before upgrading
  2. Plan maintenance window as upgrade will require brief downtime
  3. Upgrade GitLab to version 15.5.2 or later (recommended: latest stable 15.x release)
  4. Verify the upgrade completed successfully by checking GitLab version in Admin Area > Metrics and profiling > Version
  5. Test critical GitLab functions (repository access, merge requests, CI/CD pipelines) after upgrade

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-3818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3818 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