What is the severity of CVE-2019-18450?

CVE-2019-18450 has a medium severity rating due to the potential for unauthorized access resulting from insecure permissions.

How do I fix CVE-2019-18450?

To fix CVE-2019-18450, update GitLab Community or Enterprise Edition to version 12.4.1 or later.

What is the impact of CVE-2019-18450?

The impact of CVE-2019-18450 includes possible unauthorized access to project labels, which may lead to further data exposure.

Is CVE-2019-18450 present in GitLab versions after 12.4?

No, CVE-2019-18450 is not present in GitLab versions after 12.4.0 once patched.

What should I do if I cannot update to a fixed version for CVE-2019-18450?

If you cannot update, consider implementing strict access controls and monitoring to mitigate the risks associated with CVE-2019-18450.

Vulnerability/
CVE-2019-18450

medium

4.3

CWE

732

26/11/2019

5/8/2024

CVE-2019-18450

First published: Tue Nov 26 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 12.4 in the Project labels feature. It has Insecure Permissions.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-18450?
CVE-2019-18450 has a medium severity rating due to the potential for unauthorized access resulting from insecure permissions.
How do I fix CVE-2019-18450?
To fix CVE-2019-18450, update GitLab Community or Enterprise Edition to version 12.4.1 or later.
What is the impact of CVE-2019-18450?
The impact of CVE-2019-18450 includes possible unauthorized access to project labels, which may lead to further data exposure.
Is CVE-2019-18450 present in GitLab versions after 12.4?
No, CVE-2019-18450 is not present in GitLab versions after 12.4.0 once patched.
What should I do if I cannot update to a fixed version for CVE-2019-18450?
If you cannot update, consider implementing strict access controls and monitoring to mitigate the risks associated with CVE-2019-18450.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
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/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-18450?
CVE-2019-18450 has a medium severity rating due to the potential for unauthorized access resulting from insecure permissions.
How do I fix CVE-2019-18450?
To fix CVE-2019-18450, update GitLab Community or Enterprise Edition to version 12.4.1 or later.
What is the impact of CVE-2019-18450?
The impact of CVE-2019-18450 includes possible unauthorized access to project labels, which may lead to further data exposure.
Is CVE-2019-18450 present in GitLab versions after 12.4?
No, CVE-2019-18450 is not present in GitLab versions after 12.4.0 once patched.
What should I do if I cannot update to a fixed version for CVE-2019-18450?
If you cannot update, consider implementing strict access controls and monitoring to mitigate the risks associated with CVE-2019-18450.