dbcve.org
GitLabApplication

CVE-2022-3613

HIGH · 7.5 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 15.5.7 / 15.6.4 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
An issue has been discovered in GitLab CE/EE affecting all versions before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. A crafted Prometheus Server query can cause high resource consumption and may lead to Denial of Service.

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 Prometheus Server query in GitLab CE/EE versions prior to 15.5.7, 15.6.4, and 15.7.2 triggers excessive resource consumption, potentially causing denial of service. The vulnerability is exploitable remotely without authentication via malicious query input to the Prometheus integration.

MitigationUpgrade GitLab to version 15.5.7, 15.6.4, 15.7.2 or later. If immediate upgrade is not feasible, consider disabling or restricting the Prometheus integration 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:< 15.5.7>= 15.6.0, < 15.6.4>= 15.7.0, < 15.7.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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin area at /help under the version information section
    Affected if Version is earlier than 15.5.7, or falls between 15.6.0-15.6.3, or falls between 15.7.0-15.7.1
  2. Verify Prometheus integration is enabled
    Navigate to GitLab admin area > Settings > Metrics and Dashboards (or /admin/settings/_metrics) and check if 'Enable Prometheus Metrics' is toggled on; alternatively check gitlab.yml configuration file for prometheus: enabled: true
    Affected if Prometheus integration is enabled in GitLab settings or configuration
  3. Confirm Prometheus metrics endpoint is accessible
    Check if the `/api/v4/metrics` endpoint responds externally (e.g., curl -I https://your-gitlab-instance/api/v4/metrics) or verify in the GitLab admin panel that metrics are exposed
    Affected if The metrics endpoint is reachable from the network without authentication (unauthenticated access is required for exploitation)
  4. Review recent Prometheus query logs for anomalies
    Check GitLab logs (sudo gitlab-ctl tail production | grep -i prometheus) for unusually slow or resource-intensive Prometheus queries around the time of potential exploitation
    Affected if Logs show excessive query times or resource consumption from Prometheus query endpoints

You are affected if your GitLab version falls within the vulnerable ranges AND the Prometheus integration is enabled and accessible without authentication, allowing remote attackers to send malicious queries.

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.5.7 / 15.6.4 / 15.7.2 or later
Fixed in 15.5.715.6.415.7.2
Interim mitigation

Upgrade GitLab to version 15.5.7, 15.6.4, 15.7.2 or later. If immediate upgrade is not feasible, consider disabling or restricting the Prometheus integration until the patch can be applied.

Recommended fix High confidence

Upgrade to GitLab 15.5.7, 15.6.4, 15.7.2, or later (preferably latest stable 15.x release)

  1. Verify current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. Stop GitLab services with `sudo gitlab-ctl stop`
  3. Ensure you have a complete backup of the GitLab instance
  4. For package installations: run `sudo apt-get update && sudo apt-get install gitlab-ce` (or `gitlab-ee`) to upgrade to the latest version, or specify version with `sudo apt-get install gitlab-ce=15.7.2-0`
  5. Alternatively, use the omnibus GitLab upgrade commands: `curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash` followed by `sudo apt-get install gitlab-ce`
  6. After upgrade, reconfigure GitLab with `sudo gitctl reconfigure`
  7. Restart GitLab services with `sudo gitlab-ctl start`
  8. Verify the upgrade was successful and GitLab is functioning normally
Caveat Review GitLab release notes for any breaking changes 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-3613 — 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-3613 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