What is the severity of CVE-2024-0410?

The severity of CVE-2024-0410 is considered to be high due to its potential to bypass authorization checks.

How do I fix CVE-2024-0410?

To fix CVE-2024-0410, upgrade your GitLab installation to version 16.7.6, 16.8.3, or 16.9.1 or later.

Who is affected by CVE-2024-0410?

CVE-2024-0410 affects GitLab versions from 15.1 up to 16.7.6, 16.8 up to 16.8.3, and version 16.9.0.

What types of attacks can CVE-2024-0410 enable?

CVE-2024-0410 can enable unauthorized code changes by allowing developers to bypass CODEOWNERS approvals.

Is there a workaround for CVE-2024-0410?

No official workaround is recommended for CVE-2024-0410; the best action is to upgrade to a fixed version.

Vulnerability/
CVE-2024-0410

high

7.7

CWE

841

21/2/2024

3/10/2024

CVE-2024-0410: Improper Enforcement of Behavioral Workflow in GitLab

First published: Wed Feb 21 2024(Updated: )

An authorization bypass vulnerability was discovered in GitLab affecting versions 15.1 prior to 16.7.6, 16.8 prior to 16.8.3, and 16.9 prior to 16.9.1. A developer could bypass CODEOWNERS approvals by creating a merge conflict.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.1.0<16.7.6
GitLab	>=16.8.0<16.8.3
GitLab	=16.9.0

Remedy

Upgrade to versions 16.9.1, 16.8.3, 16.7.6 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-0410?
The severity of CVE-2024-0410 is considered to be high due to its potential to bypass authorization checks.
How do I fix CVE-2024-0410?
To fix CVE-2024-0410, upgrade your GitLab installation to version 16.7.6, 16.8.3, or 16.9.1 or later.
Who is affected by CVE-2024-0410?
CVE-2024-0410 affects GitLab versions from 15.1 up to 16.7.6, 16.8 up to 16.8.3, and version 16.9.0.
What types of attacks can CVE-2024-0410 enable?
CVE-2024-0410 can enable unauthorized code changes by allowing developers to bypass CODEOWNERS approvals.
Is there a workaround for CVE-2024-0410?
No official workaround is recommended for CVE-2024-0410; the best action is to upgrade to a fixed version.

agent/references
agent/remedy
agent/type
agent/description
agent/first-publish-date
agent/severity
agent/author
agent/event
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/title
agent/weakness
agent/last-modified-date
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/15.1.0
version/gitlab/16.8.0
version/gitlab/16.9.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-2024-0410?
The severity of CVE-2024-0410 is considered to be high due to its potential to bypass authorization checks.
How do I fix CVE-2024-0410?
To fix CVE-2024-0410, upgrade your GitLab installation to version 16.7.6, 16.8.3, or 16.9.1 or later.
Who is affected by CVE-2024-0410?
CVE-2024-0410 affects GitLab versions from 15.1 up to 16.7.6, 16.8 up to 16.8.3, and version 16.9.0.
What types of attacks can CVE-2024-0410 enable?
CVE-2024-0410 can enable unauthorized code changes by allowing developers to bypass CODEOWNERS approvals.
Is there a workaround for CVE-2024-0410?
No official workaround is recommended for CVE-2024-0410; the best action is to upgrade to a fixed version.