CVE-2022-2497

Description

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.

8.5

CVSS

Severity: High

CVSS 3.1 •

EPSS 4.45% Top 15%

Vendor Advisory gitlab.com Vendor Advisory gitlab.com

Affected: GitLab GitLab

References

Link	Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/362671	vendor advisory broken link
https://hackerone.com/reports/1557992	third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2497.json	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-2497?: CVE-2022-2497 has been scored as a high severity vulnerability.
How to fix CVE-2022-2497?: To fix CVE-2022-2497, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-2497 being actively exploited in the wild?: It is possible that CVE-2022-2497 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~4% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-2497?: CVE-2022-2497 affects GitLab GitLab.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.