What is the severity of CVE-2021-22245?

CVE-2021-22245 is classified as a medium severity vulnerability.

How do I fix CVE-2021-22245?

To fix CVE-2021-22245, users should upgrade to GitLab versions 13.12.9 or higher, or 14.0.7 or higher for affected installations.

What impact does CVE-2021-22245 have on GitLab?

CVE-2021-22245 allows an attacker to alter commit authorship, leading to restricted access to project pages.

What versions of GitLab are affected by CVE-2021-22245?

CVE-2021-22245 affects GitLab Community and Enterprise editions up to 13.12.8 and several versions within the 14.x range.

Is there a workaround for CVE-2021-22245?

There are no official workarounds for CVE-2021-22245; upgrading is recommended for mitigation.

Vulnerability/
CVE-2021-22245

medium

CWE

25/8/2021

3/8/2024

CVE-2021-22245: Input Validation

First published: Wed Aug 25 2021(Updated: )

Improper validation of commit author in GitLab CE/EE affecting all versions allowed an attacker to make several pages in a project impossible to view

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<13.12.9
GitLab	<13.12.9
GitLab	>=14.0.0<14.0.7
GitLab	>=14.0.0<14.0.7
GitLab	>=14.1.0<14.1.2
GitLab	>=14.1.0<14.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22245?
CVE-2021-22245 is classified as a medium severity vulnerability.
How do I fix CVE-2021-22245?
To fix CVE-2021-22245, users should upgrade to GitLab versions 13.12.9 or higher, or 14.0.7 or higher for affected installations.
What impact does CVE-2021-22245 have on GitLab?
CVE-2021-22245 allows an attacker to alter commit authorship, leading to restricted access to project pages.
What versions of GitLab are affected by CVE-2021-22245?
CVE-2021-22245 affects GitLab Community and Enterprise editions up to 13.12.8 and several versions within the 14.x range.
Is there a workaround for CVE-2021-22245?
There are no official workarounds for CVE-2021-22245; upgrading is recommended for mitigation.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/14.0.0
version/gitlab/14.1.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-22245?
CVE-2021-22245 is classified as a medium severity vulnerability.
How do I fix CVE-2021-22245?
To fix CVE-2021-22245, users should upgrade to GitLab versions 13.12.9 or higher, or 14.0.7 or higher for affected installations.
What impact does CVE-2021-22245 have on GitLab?
CVE-2021-22245 allows an attacker to alter commit authorship, leading to restricted access to project pages.
What versions of GitLab are affected by CVE-2021-22245?
CVE-2021-22245 affects GitLab Community and Enterprise editions up to 13.12.8 and several versions within the 14.x range.
Is there a workaround for CVE-2021-22245?
There are no official workarounds for CVE-2021-22245; upgrading is recommended for mitigation.