What is the severity of CVE-2022-1510?

CVE-2022-1510 has been categorized as a medium severity vulnerability.

How do I fix CVE-2022-1510?

To fix CVE-2022-1510, you should upgrade your GitLab instance to version 14.8.6 or later, or to version 14.9.4 or later.

What versions of GitLab are affected by CVE-2022-1510?

CVE-2022-1510 affects GitLab versions from 13.9 through to 14.8.6, from 14.9.0 to 14.9.4, and the version 14.10.0.

What type of attack does CVE-2022-1510 expose GitLab to?

CVE-2022-1510 exposes GitLab to potential cross-site scripting (XSS) attacks through improper handling of malicious text in the CI Editor.

Is there a workaround for CVE-2022-1510?

There is no specific workaround for CVE-2022-1510; upgrading to a patched version is strongly recommended.

Vulnerability/
CVE-2022-1510

high

7.5

CWE

1333

11/5/2022

3/8/2024

CVE-2022-1510

First published: Wed May 11 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 13.9 before 14.8.6, all versions starting from 14.9 before 14.9.4, all versions starting from 14.10 before 14.10.1. GitLab was not correctly handling malicious text in the CI Editor and CI Pipeline details page allowing the attacker to cause uncontrolled resource consumption.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.9.0<14.8.6
GitLab	>=13.9.0<14.8.6
GitLab	>=14.9.0<14.9.4
GitLab	>=14.9.0<14.9.4
GitLab	=14.10.0
GitLab	=14.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1510?
CVE-2022-1510 has been categorized as a medium severity vulnerability.
How do I fix CVE-2022-1510?
To fix CVE-2022-1510, you should upgrade your GitLab instance to version 14.8.6 or later, or to version 14.9.4 or later.
What versions of GitLab are affected by CVE-2022-1510?
CVE-2022-1510 affects GitLab versions from 13.9 through to 14.8.6, from 14.9.0 to 14.9.4, and the version 14.10.0.
What type of attack does CVE-2022-1510 expose GitLab to?
CVE-2022-1510 exposes GitLab to potential cross-site scripting (XSS) attacks through improper handling of malicious text in the CI Editor.
Is there a workaround for CVE-2022-1510?
There is no specific workaround for CVE-2022-1510; upgrading to a patched version is strongly recommended.

agent/author
agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/13.9.0
version/gitlab/14.9.0
version/gitlab/14.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-2022-1510?
CVE-2022-1510 has been categorized as a medium severity vulnerability.
How do I fix CVE-2022-1510?
To fix CVE-2022-1510, you should upgrade your GitLab instance to version 14.8.6 or later, or to version 14.9.4 or later.
What versions of GitLab are affected by CVE-2022-1510?
CVE-2022-1510 affects GitLab versions from 13.9 through to 14.8.6, from 14.9.0 to 14.9.4, and the version 14.10.0.
What type of attack does CVE-2022-1510 expose GitLab to?
CVE-2022-1510 exposes GitLab to potential cross-site scripting (XSS) attacks through improper handling of malicious text in the CI Editor.
Is there a workaround for CVE-2022-1510?
There is no specific workaround for CVE-2022-1510; upgrading to a patched version is strongly recommended.