What is the severity of CVE-2021-22241?

CVE-2021-22241 has a medium severity rating due to its potential to cause stored cross-site scripting vulnerabilities.

How do I fix CVE-2021-22241?

To fix CVE-2021-22241, upgrade your GitLab installation to the latest version that is patched against this vulnerability.

Which versions are affected by CVE-2021-22241?

CVE-2021-22241 affects all GitLab CE/EE versions starting from 14.0 up to and including 14.1.2.

Can CVE-2021-22241 be exploited remotely?

Yes, CVE-2021-22241 can be exploited remotely through the manipulation of default branch names.

Is user interaction required to exploit CVE-2021-22241?

User interaction is not required to exploit CVE-2021-22241, making it a more severe risk for vulnerable installations.

Vulnerability/
CVE-2021-22241

high

8.7

CWE

5/8/2021

3/8/2024

CVE-2021-22241: XSS

First published: Thu Aug 05 2021(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0. It was possible to exploit a stored cross-site-scripting via a specifically crafted default branch name.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
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-22241?
CVE-2021-22241 has a medium severity rating due to its potential to cause stored cross-site scripting vulnerabilities.
How do I fix CVE-2021-22241?
To fix CVE-2021-22241, upgrade your GitLab installation to the latest version that is patched against this vulnerability.
Which versions are affected by CVE-2021-22241?
CVE-2021-22241 affects all GitLab CE/EE versions starting from 14.0 up to and including 14.1.2.
Can CVE-2021-22241 be exploited remotely?
Yes, CVE-2021-22241 can be exploited remotely through the manipulation of default branch names.
Is user interaction required to exploit CVE-2021-22241?
User interaction is not required to exploit CVE-2021-22241, making it a more severe risk for vulnerable installations.

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/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-22241?
CVE-2021-22241 has a medium severity rating due to its potential to cause stored cross-site scripting vulnerabilities.
How do I fix CVE-2021-22241?
To fix CVE-2021-22241, upgrade your GitLab installation to the latest version that is patched against this vulnerability.
Which versions are affected by CVE-2021-22241?
CVE-2021-22241 affects all GitLab CE/EE versions starting from 14.0 up to and including 14.1.2.
Can CVE-2021-22241 be exploited remotely?
Yes, CVE-2021-22241 can be exploited remotely through the manipulation of default branch names.
Is user interaction required to exploit CVE-2021-22241?
User interaction is not required to exploit CVE-2021-22241, making it a more severe risk for vulnerable installations.