CVE-2019-19262
First published: Fri Jan 03 2020(Updated: )
GitLab Enterprise Edition (EE) 11.9 and later through 12.5 has Insecure Permissions.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.9.0<12.5.2 |
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-19262?
The severity of CVE-2019-19262 is considered to be moderate, impacting the GitLab Enterprise Edition with potential unauthorized access.
How do I fix CVE-2019-19262?
To fix CVE-2019-19262, upgrade GitLab Enterprise Edition to version 12.5.2 or later as recommended in security updates.
What versions are affected by CVE-2019-19262?
CVE-2019-19262 affects GitLab Enterprise Edition versions between 11.9.0 and 12.5.2 inclusive.
What are the risks associated with CVE-2019-19262?
The risks associated with CVE-2019-19262 include the potential for unauthorized users to gain access to sensitive information in GitLab.
Is there a patch available for CVE-2019-19262?
Yes, a patch is available through updating to GitLab Enterprise Edition version 12.5.2 or higher.
- agent/type
- agent/references
- 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.9.0