What is the severity of CVE-2022-2527?

CVE-2022-2527 is classified as a medium severity vulnerability.

How do I fix CVE-2022-2527?

To fix CVE-2022-2527, upgrade GitLab to version 15.1.6 or newer, 15.2.4 or newer, or 15.3.2 or newer as applicable.

Which versions are affected by CVE-2022-2527?

CVE-2022-2527 affects all GitLab CE and EE versions from 14.9 to 15.1.6, 15.2 to 15.2.4, and 15.3 to 15.3.2.

Is there a workaround for CVE-2022-2527 if I cannot upgrade immediately?

There are no specific workarounds for CVE-2022-2527; upgrading to a patched version is recommended.

Vulnerability/
CVE-2022-2527

high

CWE

17/10/2022

3/8/2024

CVE-2022-2527: XSS

Q: What type of attack does CVE-2022-2527 allow?

CVE-2022-2527 allows an authenticated attacker to inject arbitrary content into Incident Timelines.

First published: Mon Oct 17 2022(Updated: )

An issue in Incident Timelines has been discovered in GitLab CE/EE affecting all versions starting from 14.9 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2.which allowed an authenticated attacker to inject arbitrary content. A victim interacting with this content could lead to arbitrary requests.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.9.0<15.1.6
GitLab	>=14.9.0<15.1.6
GitLab	>=15.2<15.2.4
GitLab	>=15.2<15.2.4
GitLab	>=15.3<15.3.2
GitLab	>=15.3<15.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2527?
CVE-2022-2527 is classified as a medium severity vulnerability.
How do I fix CVE-2022-2527?
To fix CVE-2022-2527, upgrade GitLab to version 15.1.6 or newer, 15.2.4 or newer, or 15.3.2 or newer as applicable.
Which versions are affected by CVE-2022-2527?
CVE-2022-2527 affects all GitLab CE and EE versions from 14.9 to 15.1.6, 15.2 to 15.2.4, and 15.3 to 15.3.2.
What type of attack does CVE-2022-2527 allow?
CVE-2022-2527 allows an authenticated attacker to inject arbitrary content into Incident Timelines.
Is there a workaround for CVE-2022-2527 if I cannot upgrade immediately?
There are no specific workarounds for CVE-2022-2527; upgrading to a patched version is recommended.

agent/type
agent/references
agent/author
agent/weakness
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/14.9.0
version/gitlab/15.2
version/gitlab/15.3

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-2527?
CVE-2022-2527 is classified as a medium severity vulnerability.
How do I fix CVE-2022-2527?
To fix CVE-2022-2527, upgrade GitLab to version 15.1.6 or newer, 15.2.4 or newer, or 15.3.2 or newer as applicable.
Which versions are affected by CVE-2022-2527?
CVE-2022-2527 affects all GitLab CE and EE versions from 14.9 to 15.1.6, 15.2 to 15.2.4, and 15.3 to 15.3.2.
What type of attack does CVE-2022-2527 allow?
CVE-2022-2527 allows an authenticated attacker to inject arbitrary content into Incident Timelines.
Is there a workaround for CVE-2022-2527 if I cannot upgrade immediately?
There are no specific workarounds for CVE-2022-2527; upgrading to a patched version is recommended.