CVE-2019-12914
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 · uneditedRedbrick Shift through 3.4.3 allows an attacker to extract authentication tokens of services (such as Gmail, Outlook, etc.) used in the application.
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 · moderate confidenceRedbrick Shift through version 3.4.3 contains a vulnerability that allows attackers to extract authentication tokens for integrated third-party services (such as Gmail, Outlook, etc.) used within the application. The specific attack vector and root cause are not detailed in available sources, but the vulnerability enables unauthorized access to external service credentials.
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<= 3.4.3CVSS 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.0/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.
-
Identify installed Redbrick Shift versionLocate the Redbrick Shift installation and determine the version number, typically found in the application metadata, about screen, or version file within the installation directoryAffected if The installed version is 3.4.3 or any earlier version
-
Determine if third-party integrations existReview the Redbrick Shift configuration or settings to identify whether any external services such as email providers (Gmail, Outlook) or other third-party integrations are connected or configuredAffected if One or more third-party service integrations are configured and active in the application
-
Inspect credential storage locationsExamine the application's data directories, configuration files, or credential stores where authentication tokens for integrated services are persistedAffected if Authentication tokens for third-party services are stored in accessible locations within the application
-
Review access logs for suspicious credential retrievalSearch application logs, audit trails, or access records for any unusual or unauthorized access patterns to credential storage, token retrieval events, or API calls exposing sensitive authentication dataAffected if Logs show unexpected or unauthorized access to authentication token data
A user is affected if they run Redbrick Shift version 3.4.3 or earlier and have configured third-party service integrations, as the vulnerability allows extraction of stored authentication tokens.
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 dataUpgrade Redbrick Shift to a version beyond 3.4.3 and rotate all authentication tokens for integrated services that may have been exposed. Investigate logs for signs of token extraction or unauthorized access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12914 — 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-12914 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