What is the severity of CVE-2019-12441?

CVE-2019-12441 is classified as a high severity vulnerability due to its ability to bypass access control rules in GitLab.

How do I fix CVE-2019-12441?

To mitigate CVE-2019-12441, upgrade your GitLab installation to version 11.11.1 or later.

What impact does CVE-2019-12441 have on my GitLab instance?

CVE-2019-12441 allows unauthorized users to bypass restrictions on protected branches, potentially leading to unauthorized code changes.

What versions of GitLab are affected by CVE-2019-12441?

CVE-2019-12441 affects GitLab Community and Enterprise Editions from version 8.4.0 to 11.11.0.

Is CVE-2019-12441 fixed in future versions of GitLab?

Yes, CVE-2019-12441 has been resolved in GitLab version 11.11.1 and subsequent releases.

Vulnerability/
CVE-2019-12441

high

7.5

CWE

732

10/3/2020

4/8/2024

CVE-2019-12441

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 8.4 through 11.11. The protected branches feature contained a access control issue which resulted in a bypass of the protected branches restriction rules. It has Incorrect Access Control.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.4.0<=11.11.0
GitLab	>=8.4.0<=11.11.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-12441?
CVE-2019-12441 is classified as a high severity vulnerability due to its ability to bypass access control rules in GitLab.
How do I fix CVE-2019-12441?
To mitigate CVE-2019-12441, upgrade your GitLab installation to version 11.11.1 or later.
What impact does CVE-2019-12441 have on my GitLab instance?
CVE-2019-12441 allows unauthorized users to bypass restrictions on protected branches, potentially leading to unauthorized code changes.
What versions of GitLab are affected by CVE-2019-12441?
CVE-2019-12441 affects GitLab Community and Enterprise Editions from version 8.4.0 to 11.11.0.
Is CVE-2019-12441 fixed in future versions of GitLab?
Yes, CVE-2019-12441 has been resolved in GitLab version 11.11.1 and subsequent releases.

agent/references
agent/type
agent/weakness
agent/author
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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.4.0
version/gitlab/11.11.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-2019-12441?
CVE-2019-12441 is classified as a high severity vulnerability due to its ability to bypass access control rules in GitLab.
How do I fix CVE-2019-12441?
To mitigate CVE-2019-12441, upgrade your GitLab installation to version 11.11.1 or later.
What impact does CVE-2019-12441 have on my GitLab instance?
CVE-2019-12441 allows unauthorized users to bypass restrictions on protected branches, potentially leading to unauthorized code changes.
What versions of GitLab are affected by CVE-2019-12441?
CVE-2019-12441 affects GitLab Community and Enterprise Editions from version 8.4.0 to 11.11.0.
Is CVE-2019-12441 fixed in future versions of GitLab?
Yes, CVE-2019-12441 has been resolved in GitLab version 11.11.1 and subsequent releases.