CVE-2019-12446
First published: Tue Mar 10 2020(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 8.3 through 11.11. It allows Information Exposure through an Error Message.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=8.3.0<=11.11.0 | |
| GitLab | >=8.3.0<=11.11.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-12446?
CVE-2019-12446 is classified as a medium severity vulnerability due to the information exposure risk it poses.
How do I fix CVE-2019-12446?
To fix CVE-2019-12446, update GitLab Community or Enterprise Edition to version 11.11.1 or later.
What types of software are affected by CVE-2019-12446?
CVE-2019-12446 affects GitLab Community Edition and Enterprise Edition versions between 8.3.0 and 11.11.0.
What is the impact of CVE-2019-12446?
The impact of CVE-2019-12446 is that it allows unauthorized access to sensitive information through error messages.
Is there a workaround for CVE-2019-12446?
There is no known workaround for CVE-2019-12446, and upgrading to a patched version is the recommended action.
- 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.3.0
- version/gitlab/11.11.0