GitLabApplication
CVE-2019-14943
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in GitLab Community and Enterprise Edition 12.0 through 12.1.4. It uses Hard-coded Credentials.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceGitLab Community and Enterprise Edition versions 12.0 through 12.1.4 contain hard-coded credentials embedded in the application code or configuration. These credentials could be discovered and exploited by attackers to gain unauthorized access to the system or its resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 12.0, <= 12.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GitLab installation and versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the installed GitLab versionAffected if The displayed version falls within 12.0 to 12.1.4 inclusive
-
Check GitLab package version via command lineOn Linux systems, run `dpkg -l | grep gitlab-ee` or `rpm -qa | grep gitlab` to list the installed GitLab package and its exact version numberAffected if The package version shows a release between 12.0.0 and 12.1.4
-
Verify the exact minor versionExamine the full version string from the GitLab admin interface (Admin Area > Dashboard) or from the gitlab-rake command output for the precise version number (e.g., 12.1.0, 12.1.3, 12.1.4)Affected if The version is 12.0.x, 12.1.0, 12.1.1, 12.1.2, 12.1.3, or 12.1.4
You are affected if GitLab is installed and its version is 12.0, 12.1.0, 12.1.1, 12.1.2, 12.1.3, or 12.1.4 (any version from 12.0 through 12.1.4 inclusive).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade GitLab to a version newer than 12.1.4. Additionally, audit the installation for any unauthorized access and rotate any credentials that may have been exposed.
GitLab 12.1.5 or later (recommended: latest 12.x stable release)
- Backup your GitLab instance data before proceeding with any upgrade
- Review the GitLab upgrade documentation for your current installation method (Omnibus, source, etc.)
- Plan for appropriate maintenance window as upgrade may require downtime
- For Omnibus installations: Stop GitLab, run gitlab-ctl upgrade, or upgrade to the latest 12.x stable release
- For source installations: Follow the upgrade path from 12.1.4 to 12.1.5 or later
- After upgrade, verify that the hard-coded credentials have been removed or changed
- Ensure all default passwords/credentials are changed to unique, strong values
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14943 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data