CVE-2019-12911
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 stored for integrated external services such as Gmail and Outlook. The tokens are likely stored in an insecure manner (e.g., plaintext, weak encryption, or accessible file paths) enabling unauthorized access to connected service accounts.
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 Redbrick Shift versionLocate the Redbrick Shift installation and retrieve its version number (check application metadata, About page, or version file in the installation directory)Affected if The installed version is 3.4.3 or any earlier version (e.g., 3.4.0, 3.x, 2.x)
-
Locate stored authentication tokensSearch the Redbrick Shift installation for files or database entries containing tokens for integrated services (look for Gmail, Outlook, or external service identifiers in config files, databases, or token storage directories)Affected if Tokens for Gmail, Outlook, or other integrated services are found in storage locations within the Redbrick Shift installation
-
Examine token storage securityInspect the stored tokens to determine if they are stored in plaintext, weakly encrypted, or in files with overly permissive access permissionsAffected if Tokens are stored in plaintext, use weak/obfuscation-only encryption, or exist in files readable by unprivileged users or processes
-
Check token storage file permissionsReview file system permissions on directories and files where tokens are stored - verify they are not world-readable or accessible to unauthorized system usersAffected if Token storage files or directories have weak permissions (e.g., world-readable, group-readable without justification)
-
Search for tokens in logs or backupsSearch application logs, backup files, or temporary directories for evidence of tokens being written in insecure mannerAffected if Authentication tokens appear in log files, debug output, or backup archives
A user is affected if Redbrick Shift version 3.4.3 or lower is installed AND authentication tokens for external services are stored in an insecure manner (plaintext, weak encryption, or improper file permissions).
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 the latest patched version and rotate all exposed authentication tokens for integrated services. Review and implement secure token storage using strong encryption and proper access controls.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12911 — 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-12911 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