What is the severity of CVE-2019-18452?

CVE-2019-18452 has been classified with a medium severity due to its impact on permissions when moving issues between projects.

How do I fix CVE-2019-18452?

The recommended fix for CVE-2019-18452 is to upgrade to GitLab version 12.4.1 or later.

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

CVE-2019-18452 affects GitLab Community and Enterprise Editions from versions 11.3.0 to 12.4.0.

What consequences can occur if CVE-2019-18452 is exploited?

If exploited, CVE-2019-18452 can allow unauthorized access to sensitive project issues potentially leading to data exposure.

Is there a workaround for CVE-2019-18452?

There are no official workarounds for CVE-2019-18452; upgrading to the fixed version is necessary.

Vulnerability/
CVE-2019-18452

medium

5.3

CWE

732

26/11/2019

5/8/2024

CVE-2019-18452

First published: Tue Nov 26 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.3 through 12.4 when moving an issue to a public project from a private one. It has Insecure Permissions.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-18452?
CVE-2019-18452 has been classified with a medium severity due to its impact on permissions when moving issues between projects.
How do I fix CVE-2019-18452?
The recommended fix for CVE-2019-18452 is to upgrade to GitLab version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18452?
CVE-2019-18452 affects GitLab Community and Enterprise Editions from versions 11.3.0 to 12.4.0.
What consequences can occur if CVE-2019-18452 is exploited?
If exploited, CVE-2019-18452 can allow unauthorized access to sensitive project issues potentially leading to data exposure.
Is there a workaround for CVE-2019-18452?
There are no official workarounds for CVE-2019-18452; upgrading to the fixed version is necessary.

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/11.3.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-18452?
CVE-2019-18452 has been classified with a medium severity due to its impact on permissions when moving issues between projects.
How do I fix CVE-2019-18452?
The recommended fix for CVE-2019-18452 is to upgrade to GitLab version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18452?
CVE-2019-18452 affects GitLab Community and Enterprise Editions from versions 11.3.0 to 12.4.0.
What consequences can occur if CVE-2019-18452 is exploited?
If exploited, CVE-2019-18452 can allow unauthorized access to sensitive project issues potentially leading to data exposure.
Is there a workaround for CVE-2019-18452?
There are no official workarounds for CVE-2019-18452; upgrading to the fixed version is necessary.