What is the severity of CVE-2021-22202?

CVE-2021-22202 is considered a critical vulnerability as it allows for CSRF attacks targeting admin privileges.

How do I fix CVE-2021-22202?

To fix CVE-2021-22202, upgrade your GitLab instance to version 13.10.1 or later.

Who is affected by CVE-2021-22202?

CVE-2021-22202 affects all versions of GitLab CE and EE prior to 13.10.1, specifically impacting systems with admin users.

What type of vulnerability is CVE-2021-22202?

CVE-2021-22202 is a Cross-Site Request Forgery (CSRF) vulnerability that can be exploited via the API.

What can an attacker do with CVE-2021-22202?

An attacker exploiting CVE-2021-22202 can potentially execute unauthorized actions on behalf of an admin user.

Vulnerability/
CVE-2021-22202

medium

4.3

CWE

352

2/4/2021

3/8/2024

CVE-2021-22202: CSRF

First published: Fri Apr 02 2021(Updated: )

An issue has been discovered in GitLab CE/EE affecting all previous versions. If the victim is an admin, it was possible to issue a CSRF in System hooks through the API.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<=13.10.0
GitLab	<=13.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22202?
CVE-2021-22202 is considered a critical vulnerability as it allows for CSRF attacks targeting admin privileges.
How do I fix CVE-2021-22202?
To fix CVE-2021-22202, upgrade your GitLab instance to version 13.10.1 or later.
Who is affected by CVE-2021-22202?
CVE-2021-22202 affects all versions of GitLab CE and EE prior to 13.10.1, specifically impacting systems with admin users.
What type of vulnerability is CVE-2021-22202?
CVE-2021-22202 is a Cross-Site Request Forgery (CSRF) vulnerability that can be exploited via the API.
What can an attacker do with CVE-2021-22202?
An attacker exploiting CVE-2021-22202 can potentially execute unauthorized actions on behalf of an admin user.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.10.0

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-2021-22202?
CVE-2021-22202 is considered a critical vulnerability as it allows for CSRF attacks targeting admin privileges.
How do I fix CVE-2021-22202?
To fix CVE-2021-22202, upgrade your GitLab instance to version 13.10.1 or later.
Who is affected by CVE-2021-22202?
CVE-2021-22202 affects all versions of GitLab CE and EE prior to 13.10.1, specifically impacting systems with admin users.
What type of vulnerability is CVE-2021-22202?
CVE-2021-22202 is a Cross-Site Request Forgery (CSRF) vulnerability that can be exploited via the API.
What can an attacker do with CVE-2021-22202?
An attacker exploiting CVE-2021-22202 can potentially execute unauthorized actions on behalf of an admin user.