What is the severity of CVE-2019-18453?

CVE-2019-18453 has been classified with a high severity due to insecure permissions related to the add comments via email feature.

How do I fix CVE-2019-18453?

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

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

CVE-2019-18453 affects GitLab Community and Enterprise Editions from 11.6.0 up to 12.4.0.

What feature is impacted by CVE-2019-18453?

The add comments via email feature is impacted by CVE-2019-18453 due to insecure permissions.

Is CVE-2019-18453 present in GitLab 12.5 or later?

No, CVE-2019-18453 is not present in GitLab version 12.5 or later, as the vulnerability has been addressed.

Vulnerability/
CVE-2019-18453

medium

4.3

CWE

732

26/11/2019

5/8/2024

CVE-2019-18453

First published: Tue Nov 26 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.6 through 12.4 in the add comments via email feature. It has Insecure Permissions.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-18453?
CVE-2019-18453 has been classified with a high severity due to insecure permissions related to the add comments via email feature.
How do I fix CVE-2019-18453?
To fix CVE-2019-18453, upgrade GitLab Community or Enterprise Edition to version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18453?
CVE-2019-18453 affects GitLab Community and Enterprise Editions from 11.6.0 up to 12.4.0.
What feature is impacted by CVE-2019-18453?
The add comments via email feature is impacted by CVE-2019-18453 due to insecure permissions.
Is CVE-2019-18453 present in GitLab 12.5 or later?
No, CVE-2019-18453 is not present in GitLab version 12.5 or later, as the vulnerability has been addressed.

agent/references
agent/type
agent/weakness
agent/author
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/11.6.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-18453?
CVE-2019-18453 has been classified with a high severity due to insecure permissions related to the add comments via email feature.
How do I fix CVE-2019-18453?
To fix CVE-2019-18453, upgrade GitLab Community or Enterprise Edition to version 12.4.1 or later.
Which versions of GitLab are affected by CVE-2019-18453?
CVE-2019-18453 affects GitLab Community and Enterprise Editions from 11.6.0 up to 12.4.0.
What feature is impacted by CVE-2019-18453?
The add comments via email feature is impacted by CVE-2019-18453 due to insecure permissions.
Is CVE-2019-18453 present in GitLab 12.5 or later?
No, CVE-2019-18453 is not present in GitLab version 12.5 or later, as the vulnerability has been addressed.