dbcve.org
GitLabApplication

CVE-2022-2531

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 15.0.5 / 15.1.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 issue has been discovered in GitLab EE affecting all versions starting from 12.5 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. GitLab was not performing correct authentication on Grafana API under specific conditions allowing unauthenticated users to perform queries through a path traversal vulnerability.

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 path traversal vulnerability in GitLab EE allows unauthenticated users to make Grafana API queries due to improper authentication checks on the Grafana integration. An attacker can manipulate API paths to bypass authentication and access sensitive monitoring data.

MitigationUpgrade GitLab to version 15.0.5, 15.1.4, 15.2.1, or later. Alternatively, if immediate upgrade is not feasible, disable or restrict the Grafana integration until patching can be completed.

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:>= 12.5.0, < 15.0.5>= 15.1.0, < 15.1.4= 15.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
Low
Integrity
None
Availability
None

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

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/version
    Affected if Version is 12.5.0 through 15.0.4, 15.1.0 through 15.1.3, or exactly 15.2
  2. Verify Grafana integration is enabled
    Navigate to Admin Area > Settings > Integrations > Grafana, or check via API: GET /api/v4/integrations/:integration_name
    Affected if Grafana integration is active and has API endpoint configured
  3. Inspect Grafana API URL configuration
    Check the configured Grafana URL in GitLab settings - look for the API endpoint path that handles Grafana queries
    Affected if Grafana URL points to an accessible monitoring instance
  4. Test unauthenticated Grafana API access
    Attempt to access Grafana API endpoints through GitLab without authentication headers: GET /-/grafana/api/v0/dashboards/..%2F..%2Fapi%2Fusers (note: do not actually exploit, just verify the endpoint accepts the request)
    Affected if The GitLab Grafana endpoint responds to unauthenticated requests or returns authentication errors indicating bypass

User is affected if GitLab version falls within the vulnerable ranges AND the Grafana integration is enabled with an accessible API endpoint.

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.0.5 / 15.1.4 or later
Fixed in 15.0.515.1.4
Interim mitigation

Upgrade GitLab to version 15.0.5, 15.1.4, 15.2.1, or later. Alternatively, if immediate upgrade is not feasible, disable or restrict the Grafana integration until patching can be completed.

Recommended fix High confidence

15.0.5, 15.1.4, or 15.2.1 depending on your current major version branch

  1. Identify your current GitLab version by navigating to the GitLab admin area or running `sudo gitlab-rake gitlab:env:info`
  2. Determine which upgrade path applies based on your current version: 12.5.0-15.0.4 should upgrade to 15.0.5; 15.1.0-15.1.3 should upgrade to 15.1.4; 15.2.0 should upgrade to 15.2.1
  3. Review GitLab upgrade documentation for your specific version jump at https://docs.gitlab.com/ee/update/
  4. Back up your GitLab database and repositories before upgrading
  5. For package installations (Omnibus), run: `sudo apt-get update && sudo apt-get install gitlab-ee` or use your package manager to update to the target version
  6. For source installations, follow the upgrade guide to check out the specific tag and rebuild
  7. After upgrade, verify the GitLab version with `sudo gitlab-rake gitlab:env:info`
  8. Confirm the Grafana integration works correctly post-upgrade
Caveat Review GitLab release notes for your target version for any breaking changes; 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-2531 — 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-2531 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