What is the severity of CVE-2022-1999?

CVE-2022-1999 has a severity rating of medium due to the impact of unprivileged users being able to change label descriptions.

How do I fix CVE-2022-1999?

To fix CVE-2022-1999, update your GitLab installation to version 14.10.5 or higher, 15.0.4 or higher, or 15.1.1.

Which versions are affected by CVE-2022-1999?

CVE-2022-1999 affects GitLab versions from 8.13 to before 14.10.5, 15.0 to before 15.0.4, and version 15.1.0.

What consequences can occur due to CVE-2022-1999?

Due to CVE-2022-1999, an attacker can exploit the REST API to alter label descriptions, potentially leading to misinformation.

Is there a workaround for CVE-2022-1999?

There are no documented workarounds for CVE-2022-1999; the recommended action is to upgrade to a patched version of GitLab.

Vulnerability/
CVE-2022-1999

medium

5.3

1/7/2022

3/8/2024

CVE-2022-1999

First published: Fri Jul 01 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions from 8.13 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1. Under certain conditions, using the REST API an unprivileged user was able to change labels description.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=8.13.0<14.10.5
GitLab	>=8.13.0<14.10.5
GitLab	>=15.0.0<15.0.4
GitLab	>=15.0.0<15.0.4
GitLab	=15.1.0
GitLab	=15.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1999?
CVE-2022-1999 has a severity rating of medium due to the impact of unprivileged users being able to change label descriptions.
How do I fix CVE-2022-1999?
To fix CVE-2022-1999, update your GitLab installation to version 14.10.5 or higher, 15.0.4 or higher, or 15.1.1.
Which versions are affected by CVE-2022-1999?
CVE-2022-1999 affects GitLab versions from 8.13 to before 14.10.5, 15.0 to before 15.0.4, and version 15.1.0.
What consequences can occur due to CVE-2022-1999?
Due to CVE-2022-1999, an attacker can exploit the REST API to alter label descriptions, potentially leading to misinformation.
Is there a workaround for CVE-2022-1999?
There are no documented workarounds for CVE-2022-1999; the recommended action is to upgrade to a patched version of GitLab.

agent/references
agent/type
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/8.13.0
version/gitlab/15.0.0
version/gitlab/15.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-2022-1999?
CVE-2022-1999 has a severity rating of medium due to the impact of unprivileged users being able to change label descriptions.
How do I fix CVE-2022-1999?
To fix CVE-2022-1999, update your GitLab installation to version 14.10.5 or higher, 15.0.4 or higher, or 15.1.1.
Which versions are affected by CVE-2022-1999?
CVE-2022-1999 affects GitLab versions from 8.13 to before 14.10.5, 15.0 to before 15.0.4, and version 15.1.0.
What consequences can occur due to CVE-2022-1999?
Due to CVE-2022-1999, an attacker can exploit the REST API to alter label descriptions, potentially leading to misinformation.
Is there a workaround for CVE-2022-1999?
There are no documented workarounds for CVE-2022-1999; the recommended action is to upgrade to a patched version of GitLab.