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.

Vulnerability/
CVE-2022-2497

high

8.5

5/8/2022

3/8/2024

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

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

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.