What is the severity of CVE-2022-1423?

CVE-2022-1423 is considered a high severity vulnerability due to its potential for cache poisoning by malicious actors with Developer privileges.

How do I fix CVE-2022-1423?

To mitigate CVE-2022-1423, upgrade GitLab to version 14.8.6 or later, or version 14.9.4 or later, or version 14.10.1 or later.

Who is affected by CVE-2022-1423?

CVE-2022-1423 affects all GitLab CE/EE versions from 1.0.2 before 14.8.6, from 14.9.0 before 14.9.4, and from 14.10.0 before 14.10.1.

What type of vulnerability is CVE-2022-1423?

CVE-2022-1423 is classified as an improper access control vulnerability within the CI/CD cache mechanism.

Can a user with lower privileges exploit CVE-2022-1423?

No, CVE-2022-1423 requires a user to have Developer privileges to exploit the vulnerability.

Vulnerability/
CVE-2022-1423

high

8.8

CWE

862

19/5/2022

3/8/2024

CVE-2022-1423

First published: Thu May 19 2022(Updated: )

Improper access control in the CI/CD cache mechanism in GitLab CE/EE affecting all versions starting from 1.0.2 before 14.8.6, all versions from 14.9.0 before 14.9.4, and all versions from 14.10.0 before 14.10.1 allows a malicious actor with Developer privileges to perform cache poisoning leading to arbitrary code execution in protected branches

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

Affected Software	Affected Version	How to fix
GitLab	>=1.0.2<14.8.6
GitLab	>=1.0.2<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-1423?
CVE-2022-1423 is considered a high severity vulnerability due to its potential for cache poisoning by malicious actors with Developer privileges.
How do I fix CVE-2022-1423?
To mitigate CVE-2022-1423, upgrade GitLab to version 14.8.6 or later, or version 14.9.4 or later, or version 14.10.1 or later.
Who is affected by CVE-2022-1423?
CVE-2022-1423 affects all GitLab CE/EE versions from 1.0.2 before 14.8.6, from 14.9.0 before 14.9.4, and from 14.10.0 before 14.10.1.
What type of vulnerability is CVE-2022-1423?
CVE-2022-1423 is classified as an improper access control vulnerability within the CI/CD cache mechanism.
Can a user with lower privileges exploit CVE-2022-1423?
No, CVE-2022-1423 requires a user to have Developer privileges to exploit the vulnerability.

agent/author
agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
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/1.0.2
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-1423?
CVE-2022-1423 is considered a high severity vulnerability due to its potential for cache poisoning by malicious actors with Developer privileges.
How do I fix CVE-2022-1423?
To mitigate CVE-2022-1423, upgrade GitLab to version 14.8.6 or later, or version 14.9.4 or later, or version 14.10.1 or later.
Who is affected by CVE-2022-1423?
CVE-2022-1423 affects all GitLab CE/EE versions from 1.0.2 before 14.8.6, from 14.9.0 before 14.9.4, and from 14.10.0 before 14.10.1.
What type of vulnerability is CVE-2022-1423?
CVE-2022-1423 is classified as an improper access control vulnerability within the CI/CD cache mechanism.
Can a user with lower privileges exploit CVE-2022-1423?
No, CVE-2022-1423 requires a user to have Developer privileges to exploit the vulnerability.