What is the severity of CVE-2022-2531?

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

How do I fix CVE-2022-2531?

To fix CVE-2022-2531, upgrade your GitLab EE installation to version 15.0.5, 15.1.4, or 15.2.1 or later.

What specific GitLab versions are affected by CVE-2022-2531?

CVE-2022-2531 affects GitLab EE versions from 12.5 up to, but not including, 15.0.5, 15.1 up to 15.1.4, and 15.2 up to 15.2.1.

What type of attack is CVE-2022-2531 associated with?

CVE-2022-2531 is associated with improper authentication on the Grafana API.

Is a workaround available for CVE-2022-2531?

No official workaround is provided for CVE-2022-2531; upgrading to a patched version is recommended.

Vulnerability/
CVE-2022-2531

medium

5.3

CWE

5/8/2022

3/8/2024

CVE-2022-2531: Path Traversal

First published: Fri Aug 05 2022(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 12.5 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. GitLab was not performing correct authentication on Grafana API under specific conditions allowing unauthenticated users to perform queries through a path traversal vulnerability.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.5.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2531?
CVE-2022-2531 is classified as a medium severity vulnerability.
How do I fix CVE-2022-2531?
To fix CVE-2022-2531, upgrade your GitLab EE installation to version 15.0.5, 15.1.4, or 15.2.1 or later.
What specific GitLab versions are affected by CVE-2022-2531?
CVE-2022-2531 affects GitLab EE versions from 12.5 up to, but not including, 15.0.5, 15.1 up to 15.1.4, and 15.2 up to 15.2.1.
What type of attack is CVE-2022-2531 associated with?
CVE-2022-2531 is associated with improper authentication on the Grafana API.
Is a workaround available for CVE-2022-2531?
No official workaround is provided for CVE-2022-2531; upgrading to a patched version is recommended.

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

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-2531?
CVE-2022-2531 is classified as a medium severity vulnerability.
How do I fix CVE-2022-2531?
To fix CVE-2022-2531, upgrade your GitLab EE installation to version 15.0.5, 15.1.4, or 15.2.1 or later.
What specific GitLab versions are affected by CVE-2022-2531?
CVE-2022-2531 affects GitLab EE versions from 12.5 up to, but not including, 15.0.5, 15.1 up to 15.1.4, and 15.2 up to 15.2.1.
What type of attack is CVE-2022-2531 associated with?
CVE-2022-2531 is associated with improper authentication on the Grafana API.
Is a workaround available for CVE-2022-2531?
No official workaround is provided for CVE-2022-2531; upgrading to a patched version is recommended.