What is the severity of CVE-2022-1431?

The severity of CVE-2022-1431 is classified as critical due to its impact on the security of the GitLab instance.

How do I fix CVE-2022-1431?

To fix CVE-2022-1431, you should upgrade your GitLab instance to version 14.8.6 or later, or to 14.9.4 or later if on the 14.9 series.

What versions of GitLab are affected by CVE-2022-1431?

CVE-2022-1431 affects all GitLab versions from 12.10 to before 14.8.6, from 14.9 to before 14.9.4, and from 14.10 to before 14.10.1.

Can CVE-2022-1431 be exploited remotely?

Yes, CVE-2022-1431 can be exploited remotely by sending malicious requests to the PyPi API endpoint.

What should I do if I cannot immediately update due to CVE-2022-1431?

If you cannot update immediately due to CVE-2022-1431, consider implementing network segmentation or rate limiting to mitigate potential exploitation.

Vulnerability/
CVE-2022-1431

medium

5.3

CWE

20 79

10/5/2022

3/8/2024

CVE-2022-1431: Input Validation

First published: Tue May 10 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 12.10 before 14.8.6, all versions starting from 14.9 before 14.9.4, all versions starting from 14.10 before 14.10.1. GitLab was not correctly handling malicious requests to the PyPi API endpoint allowing the attacker to cause uncontrolled resource consumption.

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

Affected Software	Affected Version	How to fix
GitLab	>=12.10.0<14.8.6
GitLab	>=12.10.0<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-1431?
The severity of CVE-2022-1431 is classified as critical due to its impact on the security of the GitLab instance.
How do I fix CVE-2022-1431?
To fix CVE-2022-1431, you should upgrade your GitLab instance to version 14.8.6 or later, or to 14.9.4 or later if on the 14.9 series.
What versions of GitLab are affected by CVE-2022-1431?
CVE-2022-1431 affects all GitLab versions from 12.10 to before 14.8.6, from 14.9 to before 14.9.4, and from 14.10 to before 14.10.1.
Can CVE-2022-1431 be exploited remotely?
Yes, CVE-2022-1431 can be exploited remotely by sending malicious requests to the PyPi API endpoint.
What should I do if I cannot immediately update due to CVE-2022-1431?
If you cannot update immediately due to CVE-2022-1431, consider implementing network segmentation or rate limiting to mitigate potential exploitation.

agent/weakness
agent/author
agent/type
agent/references
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/12.10.0
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-1431?
The severity of CVE-2022-1431 is classified as critical due to its impact on the security of the GitLab instance.
How do I fix CVE-2022-1431?
To fix CVE-2022-1431, you should upgrade your GitLab instance to version 14.8.6 or later, or to 14.9.4 or later if on the 14.9 series.
What versions of GitLab are affected by CVE-2022-1431?
CVE-2022-1431 affects all GitLab versions from 12.10 to before 14.8.6, from 14.9 to before 14.9.4, and from 14.10 to before 14.10.1.
Can CVE-2022-1431 be exploited remotely?
Yes, CVE-2022-1431 can be exploited remotely by sending malicious requests to the PyPi API endpoint.
What should I do if I cannot immediately update due to CVE-2022-1431?
If you cannot update immediately due to CVE-2022-1431, consider implementing network segmentation or rate limiting to mitigate potential exploitation.