CVE-2019-18457
First published: Tue Nov 26 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 11.8 through 12.4 when handling Security tokens.. It has Insecure Permissions.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.8.0<=12.4.0 | |
| GitLab | >=11.8.0<=12.4.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-18457?
CVE-2019-18457 has a medium severity rating due to the risk of unauthorized access resulting from insecure permissions.
How do I fix CVE-2019-18457?
To fix CVE-2019-18457, update your GitLab installation to version 12.4.1 or later.
What systems are affected by CVE-2019-18457?
CVE-2019-18457 affects GitLab Community Edition and Enterprise Edition versions from 11.8.0 to 12.4.0.
What type of vulnerability is CVE-2019-18457?
CVE-2019-18457 is categorized as an issue related to insecure permissions in GitLab.
Who can exploit CVE-2019-18457?
An attacker with limited access could exploit CVE-2019-18457 to gain enhanced permissions and access sensitive data.
- 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.8.0
- version/gitlab/12.4.0