dbcve.org
GitLabApplication

CVE-2022-2497

MEDIUM · 6.4 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 →
70/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
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.6 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. A malicious developer could exfiltrate an integration's access token by modifying the integration URL such that authenticated requests are sent to an attacker controlled server.

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

In GitLab integrations, a developer-level user can modify an integration's URL to point to an attacker-controlled server. When GitLab makes authenticated requests to the integration (e.g., webhooks), it includes the integration's access token, which gets exfiltrated to the attacker's server.

MitigationUpgrade GitLab to version 15.0.5, 15.1.4, 15.2.1 or later. Additionally, audit existing integration configurations for unauthorized or suspicious URLs and restrict developer access to integration settings until patched.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 your GitLab version
    Navigate to the Admin Area (or Help > Version) in GitLab to find the exact version number
    Affected if Version is >=12.6.0 and <15.0.5, OR >=15.1.0 and <15.1.4, OR equals 15.2 exactly
  2. Identify configured integrations
    Review integrations at the instance level (Admin Area > Integrations), group level (Group > Settings > Integrations), and project level (Project > Settings > Integrations) to see which integrations have URLs and tokens configured
    Affected if Any integrations are enabled with configured URLs and access tokens
  3. Audit user permissions for integration settings
    Review role permissions in GitLab: check if Developer role users have access to create or modify integration configurations in projects or groups
    Affected if Developer-level users have permission to modify integration settings
  4. Inspect integration URLs for suspicious destinations
    Examine all integration webhook URLs and verify they point to expected, trusted domains; look for URLs on unfamiliar or external servers
    Affected if Any integration URL points to an untrusted or attacker-controlled domain

You are affected if your GitLab version is in the vulnerable range AND you have integrations configured that Developer users can modify, particularly if those integrations point to external or untrusted 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.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. Additionally, audit existing integration configurations for unauthorized or suspicious URLs and restrict developer access to integration settings until patched.

Recommended fix High confidence

Upgrade to GitLab 15.0.5+, 15.1.4+, 15.2.1+, or the latest stable release (15.6+ recommended) depending on your current branch

  1. 1. Identify your current GitLab version by navigating to the GitLab admin area or checking the /help page
  2. 2. For GitLab versions >= 12.6.0 and < 15.0.5: Upgrade to version 15.0.5 or later (preferably the latest 15.0.x stable release)
  3. 3. For GitLab versions >= 15.1.0 and < 15.1.4: Upgrade to version 15.1.4 or later (preferably the latest 15.1.x stable release)
  4. 4. For GitLab version 15.2.x: Upgrade to version 15.2.1 or later (preferably the latest 15.2.x stable release)
  5. 5. For any newer affected minor version, upgrade to the latest stable release available from GitLab (currently 15.6.x or higher as of the patch dates)
  6. 6. Review integration settings after upgrade to ensure no unauthorized URL changes were made
  7. 7. Rotate any integration tokens that may have been exposed during the vulnerability window
Caveat Review GitLab upgrade guides for version-specific breaking changes between your current version and target version; major version jumps (e.g., 12.x to 15.x) 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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