GitLabApplication
CVE-2019-19314
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 · uneditedGitLab EE 8.4 through 12.5, 12.4.3, and 12.3.6 stored several tokens in plaintext.
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 · high confidenceGitLab Enterprise Edition versions 8.4 through 12.5, 12.4.3, and 12.3.6 stored several authentication tokens in plaintext in the database rather than using proper encryption or hashing, allowing attackers with database access to retrieve these sensitive tokens.
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
>= 8.4.0, < 12.3.8>= 12.4.0, < 12.4.5>= 12.5.0, < 12.5.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under /admin/about. Alternatively, check the version file at /opt/gitlab/version-manifest.txtAffected if Version is >= 8.4.0 and < 12.3.8, OR >= 12.4.0 and < 12.4.5, OR >= 12.5.0 and < 12.5.2
-
Access GitLab PostgreSQL databaseConnect to the GitLab database using `sudo gitlab-psql -d gitlabhq_production` or via the Rails console with `sudo gitlab-rails console -e production`Affected if Database access is possible (indicates potential exposure risk)
-
Query for plaintext authentication tokensRun SQL query: `SELECT type, token, expires_at FROM personal_access_tokens WHERE token IS NOT NULL AND token NOT LIKE '$2a$%';` (tokens should be bcrypt hashed starting with $2a$ if properly stored)Affected if Any rows returned show tokens not starting with $2a$ (indicating plaintext storage)
-
Check for other token types in databaseQuery: `SELECT table_name, column_name FROM information_schema.columns WHERE table_schema = 'public' AND column_name LIKE '%token%';` then inspect tables for plaintext values in token columnsAffected if Token columns contain readable strings instead of hashed/bcrypt values
If GitLab version falls within the affected range AND plaintext tokens are found in the database, the environment is vulnerable to CVE-2019-19314.
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.
From vendor data12.3.812.4.512.5.2
Upgrade GitLab EE to a patched version beyond 12.5, 12.4.3, and 12.3.6. Additionally, rotate any tokens that may have been exposed since the vulnerability allowed plaintext storage.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19314 — 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-19314 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