What is the severity of CVE-2022-4143?

CVE-2022-4143 has a severity rating that indicates a significant security risk due to unauthorized merging of unapproved merge requests.

How do I fix CVE-2022-4143?

To fix CVE-2022-4143, upgrade GitLab to version 15.8.5 or later, 15.9.4 or later, or 15.10.1.

Which GitLab versions are affected by CVE-2022-4143?

CVE-2022-4143 affects GitLab versions from 15.7 before 15.8.5, from 15.9 before 15.9.4, and from 15.10 before 15.10.1.

What types of issues does CVE-2022-4143 allow?

CVE-2022-4143 allows crafted, unapproved merge requests to be introduced and merged without proper authorization.

Is CVE-2022-4143 a known exploitation case?

As of the latest updates, there are reports of CVE-2022-4143 being actively exploited in the wild.

Vulnerability/
CVE-2022-4143

medium

6.4

CWE

367 362

28/6/2023

3/12/2024

CVE-2022-4143: Race Condition

First published: Wed Jun 28 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 15.7 before 15.8.5, from 15.9 before 15.9.4, and from 15.10 before 15.10.1 that allows for crafted, unapproved MRs to be introduced and merged without authorization

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.7.0<15.8.5
GitLab	>=15.7.0<15.8.5
GitLab	>=15.9.0<15.9.4
GitLab	>=15.9.0<15.9.4
GitLab	=15.10.0
GitLab	=15.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-4143?
CVE-2022-4143 has a severity rating that indicates a significant security risk due to unauthorized merging of unapproved merge requests.
How do I fix CVE-2022-4143?
To fix CVE-2022-4143, upgrade GitLab to version 15.8.5 or later, 15.9.4 or later, or 15.10.1.
Which GitLab versions are affected by CVE-2022-4143?
CVE-2022-4143 affects GitLab versions from 15.7 before 15.8.5, from 15.9 before 15.9.4, and from 15.10 before 15.10.1.
What types of issues does CVE-2022-4143 allow?
CVE-2022-4143 allows crafted, unapproved merge requests to be introduced and merged without proper authorization.
Is CVE-2022-4143 a known exploitation case?
As of the latest updates, there are reports of CVE-2022-4143 being actively exploited in the wild.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
agent/severity
agent/weakness
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/15.7.0
version/gitlab/15.9.0
version/gitlab/15.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-4143?
CVE-2022-4143 has a severity rating that indicates a significant security risk due to unauthorized merging of unapproved merge requests.
How do I fix CVE-2022-4143?
To fix CVE-2022-4143, upgrade GitLab to version 15.8.5 or later, 15.9.4 or later, or 15.10.1.
Which GitLab versions are affected by CVE-2022-4143?
CVE-2022-4143 affects GitLab versions from 15.7 before 15.8.5, from 15.9 before 15.9.4, and from 15.10 before 15.10.1.
What types of issues does CVE-2022-4143 allow?
CVE-2022-4143 allows crafted, unapproved merge requests to be introduced and merged without proper authorization.
Is CVE-2022-4143 a known exploitation case?
As of the latest updates, there are reports of CVE-2022-4143 being actively exploited in the wild.