CVE-2022-2527

Description

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.

Category

7.3
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.15%
Third-Party Advisory gitlab.com Third-Party Advisory gitlab.com Third-Party Advisory hackerone.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/368676 third party advisory
https://hackerone.com/reports/1647446 third party advisory permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2527.json third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-2527?
CVE-2022-2527 has been scored as a high severity vulnerability.
How to fix CVE-2022-2527?
To fix CVE-2022-2527, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-2527 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-2527 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-2527?
CVE-2022-2527 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.