What is the severity of CVE-2019-14943?

CVE-2019-14943 has been rated as a critical severity vulnerability due to the presence of hard-coded credentials.

How do I fix CVE-2019-14943?

To remediate CVE-2019-14943, upgrade your GitLab installation to version 12.1.6 or later.

What versions are affected by CVE-2019-14943?

CVE-2019-14943 affects GitLab Community and Enterprise Editions from version 12.0 to 12.1.4.

What impact does CVE-2019-14943 have on GitLab?

CVE-2019-14943 allows unauthorized access due to hard-coded credentials, potentially compromising sensitive data.

Is there a workaround for CVE-2019-14943?

There is no official workaround for CVE-2019-14943; patching to a secure version is recommended.

Vulnerability/
CVE-2019-14943

critical

9.8

CWE

798

29/8/2019

5/8/2024

CVE-2019-14943

First published: Thu Aug 29 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4. It uses Hard-coded Credentials.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=12.0<=12.1.4
GitLab	>=12.0<=12.1.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-14943?
CVE-2019-14943 has been rated as a critical severity vulnerability due to the presence of hard-coded credentials.
How do I fix CVE-2019-14943?
To remediate CVE-2019-14943, upgrade your GitLab installation to version 12.1.6 or later.
What versions are affected by CVE-2019-14943?
CVE-2019-14943 affects GitLab Community and Enterprise Editions from version 12.0 to 12.1.4.
What impact does CVE-2019-14943 have on GitLab?
CVE-2019-14943 allows unauthorized access due to hard-coded credentials, potentially compromising sensitive data.
Is there a workaround for CVE-2019-14943?
There is no official workaround for CVE-2019-14943; patching to a secure version is recommended.

agent/type
agent/references
agent/severity
agent/weakness
agent/author
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/12.0
version/gitlab/12.1.4

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-14943?
CVE-2019-14943 has been rated as a critical severity vulnerability due to the presence of hard-coded credentials.
How do I fix CVE-2019-14943?
To remediate CVE-2019-14943, upgrade your GitLab installation to version 12.1.6 or later.
What versions are affected by CVE-2019-14943?
CVE-2019-14943 affects GitLab Community and Enterprise Editions from version 12.0 to 12.1.4.
What impact does CVE-2019-14943 have on GitLab?
CVE-2019-14943 allows unauthorized access due to hard-coded credentials, potentially compromising sensitive data.
Is there a workaround for CVE-2019-14943?
There is no official workaround for CVE-2019-14943; patching to a secure version is recommended.