What is the severity of CVE-2019-18446?

CVE-2019-18446 is considered a medium severity vulnerability due to its potential to allow unauthorized access.

How do I fix CVE-2019-18446?

To fix CVE-2019-18446, users should upgrade their GitLab installation to version 12.4.1 or later.

Which versions of GitLab are affected by CVE-2019-18446?

CVE-2019-18446 affects GitLab Community and Enterprise Editions from version 8.15.0 up to 12.4.0.

What type of vulnerability is CVE-2019-18446?

CVE-2019-18446 is classified as an Insecure Permissions vulnerability.

Can CVE-2019-18446 lead to data exposure?

Yes, CVE-2019-18446 can potentially lead to unauthorized data exposure if not mitigated.

Vulnerability/
CVE-2019-18446

medium

5.5

CWE

732

26/11/2019

5/8/2024

CVE-2019-18446

First published: Tue Nov 26 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 8.15 through 12.4. It has Insecure Permissions (issue 1 of 2).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.15.0<=12.4.0
GitLab	>=8.15.0<=12.4.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-18446?
CVE-2019-18446 is considered a medium severity vulnerability due to its potential to allow unauthorized access.
How do I fix CVE-2019-18446?
To fix CVE-2019-18446, users should upgrade their GitLab installation to version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18446?
CVE-2019-18446 affects GitLab Community and Enterprise Editions from version 8.15.0 up to 12.4.0.
What type of vulnerability is CVE-2019-18446?
CVE-2019-18446 is classified as an Insecure Permissions vulnerability.
Can CVE-2019-18446 lead to data exposure?
Yes, CVE-2019-18446 can potentially lead to unauthorized data exposure if not mitigated.

agent/references
agent/type
agent/author
agent/weakness
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/8.15.0
version/gitlab/12.4.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-18446?
CVE-2019-18446 is considered a medium severity vulnerability due to its potential to allow unauthorized access.
How do I fix CVE-2019-18446?
To fix CVE-2019-18446, users should upgrade their GitLab installation to version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18446?
CVE-2019-18446 affects GitLab Community and Enterprise Editions from version 8.15.0 up to 12.4.0.
What type of vulnerability is CVE-2019-18446?
CVE-2019-18446 is classified as an Insecure Permissions vulnerability.
Can CVE-2019-18446 lead to data exposure?
Yes, CVE-2019-18446 can potentially lead to unauthorized data exposure if not mitigated.