ShiftApplication · Rdbrck

CVE-2019-8932

HIGH · 7.5 CVSS v3.0 Published 2019-07-17
Fix available
A fix is available. Upgrade to after 3.4.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Redbrick 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 confidence

Redbrick Shift through version 3.4.3 contains a vulnerability that allows unauthenticated attackers to extract authentication tokens for integrated third-party services (such as Gmail, Outlook, and similar). This likely involves improper storage, insufficient encryption, or an information disclosure flaw that exposes stored credentials or session tokens used by the application.

MitigationUpgrade Redbrick Shift to a version beyond 3.4.3 that addresses the token extraction vulnerability. If no patch is available, review and rotate all stored authentication tokens for integrated services immediately and implement additional access controls or encryption.

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
ShiftApplication
Affected:<= 3.4.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Redbrick Shift installation
    Locate the Redbrick Shift application in your environment - check installed software listings, application directories, or service inventories for 'Redbrick Shift' or 'Rdbrick Shift' entries
    Affected if Redbrick Shift is present in the environment
  2. Determine installed version
    Query the application for its version number - this is typically found in the application UI, a version info file, or via a command-line flag like '--version' or '-v'
    Affected if The installed version is 3.4.3 or any earlier version (versions <= 3.4.3)
  3. Check for third-party service integrations
    Examine the application configuration or settings for any integrated external services such as Gmail, Outlook, or similar third-party APIs that use authentication tokens
    Affected if One or more third-party services (email, calendar, or similar) are connected and storing authentication tokens within the application
  4. Inspect token storage location
    Locate where the application stores authentication tokens - check configuration files, databases, or credential storage directories that the application uses for integrated services
    Affected if Credentials or tokens are found stored in plaintext, weakly encrypted, or in accessible locations without proper access controls
  5. Verify unauthenticated access exposure
    Test whether the token storage or retrieval endpoints are accessible without authentication - check API endpoints, web paths, or file system permissions that could allow anonymous access
    Affected if Token storage is accessible without authentication or proper authorization checks

You are affected if Redbrick Shift version 3.4.3 or earlier is installed AND third-party service integrations are configured, as the vulnerability allows unauthenticated extraction of stored authentication tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.4.3
Interim mitigation

Upgrade Redbrick Shift to a version beyond 3.4.3 that addresses the token extraction vulnerability. If no patch is available, review and rotate all stored authentication tokens for integrated services immediately and implement additional access controls or encryption.

Fix this in Shift Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8932 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8932 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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