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.

Vulnerability/
CVE-2019-19314

high

7.5

CWE

312

5/1/2020

5/8/2024

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

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

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-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.