CVE-2019-19314
First published: Sun Jan 05 2020(Updated: )
GitLab EE 8.4 through 12.5, 12.4.3, and 12.3.6 stored several tokens in plaintext.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=8.4.0<12.3.8 | |
| GitLab | >=12.4.0<12.4.5 | |
| GitLab | >=12.5.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-19314?
CVE-2019-19314 has a moderate severity rating due to the storage of tokens in plaintext, which can lead to unauthorized access.
How do I fix CVE-2019-19314?
To fix CVE-2019-19314, update GitLab EE to version 12.5.1 or later.
What versions of GitLab are affected by CVE-2019-19314?
CVE-2019-19314 affects GitLab EE versions from 8.4 to 12.5, including specific versions 12.4.3 and 12.3.6.
Is there a risk of data exposure with CVE-2019-19314?
Yes, CVE-2019-19314 poses a risk of data exposure as it allows tokens stored in plaintext to be compromised.
Who should be concerned about CVE-2019-19314?
Organizations using affected versions of GitLab EE should be concerned about CVE-2019-19314 due to the potential security risks.
- agent/type
- agent/references
- 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/8.4.0
- version/gitlab/12.4.0
- version/gitlab/12.5.0