CVE-2019-12912
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 emails 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 an information disclosure vulnerability that allows unauthenticated or low-privilege attackers to enumerate and extract email addresses associated with external services (such as Gmail, Outlook, or other integrated platforms) configured within the application. The vulnerability likely stems from improper access controls on an API endpoint or functionality that returns service configuration data.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 installation and versionLocate the Redbrick Shift installation directory or check the application help/about section for the exact version number. Compare against the affected range: versions 3.4.3 and below.Affected if The installed version is Redbrick Shift at revision 3.4.3 or any earlier version.
-
Determine if external email services are configuredInspect the application configuration files or administrative settings for entries related to integrated external services such as Gmail, Outlook, or other mail platforms. Look for stored credentials, API configurations, or service account mappings.Affected if External email or collaboration services (such as Gmail, Outlook, or similar) are connected or configured within the application.
-
Identify accessible API endpoints returning configuration dataReview the application's API documentation or traffic logs to locate endpoints that return service configuration or user data. Common patterns include endpoints under /api/config, /api/services, or similar paths that expose integration settings.Affected if An API endpoint exists that returns service configuration data including email addresses or service identifiers.
-
Test unauthenticated access to service configuration dataAttempt to access the suspected API endpoints without providing authentication credentials or using a low-privilege account. Observe whether the response includes email addresses associated with configured external services.Affected if Unauthenticated or low-privilege users can retrieve email addresses or sensitive service configuration details through API requests.
A user is affected if they are running Redbrick Shift version 3.4.3 or lower with external services (such as Gmail, Outlook, or other integrated platforms) configured, and the application exposes email addresses to unauthenticated or low-privilege users through its API.
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 dataImplement proper authentication and role-based access controls on all endpoints that return service configuration or user data. Additionally, redact or hash sensitive identifiers like email addresses when returned to unauthorized users.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12912 — 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-12912 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