CVE-2022-2497Network attack vector

Token theft via retained integration credentials

Published Aug 5, 2022 · Updated Aug 3, 2024

Information exposure in affected GitLab CE/EE releases allows remote authenticated users to steal integration access tokens through changed URLs. When a project maintainer replaces an integration's destination URL, GitLab retains the write-only stored token and sends it in an authenticated test or webhook request to the replacement server. Maintainer-level project access, a previously configured integration token, and a release from 12.6 through 15.0.4, 15.1 through 15.1.3, or 15.2.0 are required; compromise extends to the external service authorized by that token.

CVSS severity8.5
High
EPSS probability1.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information exposure in affected GitLab CE/EE releases allows remote authenticated users to steal integration access tokens through changed URLs. When a project maintainer replaces an integration's destination URL, GitLab retains the write-only stored token and sends it in an authenticated test or webhook request to the replacement server. Maintainer-level project access, a previously configured integration token, and a release from 12.6 through 15.0.4, 15.1 through 15.1.3, or 15.2.0 are required; compromise extends to the external service authorized by that token.

The record

CVE
CVE-2022-2497
Published
Aug 5, 2022
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
T1528
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 5, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=12.6, <15.0.5
  2. Affected versionversion=>=15.1, <15.1.4
  3. Affected versionversion=>=15.2, <15.2.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=12.6, <15.0.5; version=>=15.1, <15.1.4; version=>=15.2, <15.2.1

Published CVSS scores

8.5GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1528Steal Application Access Token

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo