CVE-2022-2497
First published: Fri Aug 05 2022(Updated: )
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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=12.6.0<15.0.5 | |
| GitLab | >=15.1.0<15.1.4 | |
| GitLab | =15.2 | |
| GitLab | >=12.6.0<15.0.5 | |
| GitLab | >=15.1.0<15.1.4 | |
| GitLab | =15.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-2497?
CVE-2022-2497 has been classified as a medium severity vulnerability.
How do I fix CVE-2022-2497?
To fix CVE-2022-2497, upgrade GitLab to version 15.0.5, 15.1.4, or 15.2.1 or later.
What versions are affected by CVE-2022-2497?
CVE-2022-2497 affects all GitLab CE/EE versions from 12.6 up to 15.0.5, 15.1 up to 15.1.4, and 15.2 up to 15.2.1.
Who is affected by CVE-2022-2497?
CVE-2022-2497 potentially affects any instance of GitLab that uses integrations and is running the specified vulnerable versions.
What are the implications of CVE-2022-2497?
CVE-2022-2497 allows a malicious developer to exfiltrate integration access tokens, posing a significant security risk.
- agent/type
- agent/references
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/12.6.0
- version/gitlab/15.1.0
- version/gitlab/15.2