CVE-2017-9370
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 · uneditedAn information disclosure / elevation of privilege vulnerability in the BlackBerry Workspaces Server could potentially allow an attacker who has legitimate access to BlackBerry Workspaces to gain access to another user's workspace by making multiple login requests to the server.
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 confidenceImproper session handling in BlackBerry Workspaces Server allows an authenticated attacker with legitimate access to exploit the login mechanism through multiple sequential requests, enabling unauthorized access to other users' workspaces by hijacking or circumventing session boundaries.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 BlackBerry Workspaces Server installationSearch the system for BlackBerry Workspaces Server components, services, or known installation directories. Check running services for processes related to BlackBerry Workspaces.Affected if BlackBerry Workspaces Server is installed and running in the environment
-
Determine BlackBerry Workspaces versionLocate version information through the product's admin interface, installation directory metadata, or system information tools. Compare the installed version against the affected range.Affected if Any version of BlackBerry Workspaces is installed (all versions are affected)
-
Verify session management is enabledCheck the BlackBerry Workspaces admin console or configuration files for session management module settings. Confirm whether session handling features are active.Affected if Session management is enabled and active on the server
-
Inspect session configuration for boundary controlsReview session configuration files or the admin interface for session boundary settings. Look for settings related to session isolation, token validation, or cross-user access controls.Affected if Session boundary controls are present but may be improperly enforced (the vulnerability allows session hijacking/cross-user access)
-
Review authentication logs for sequential requestsExamine BlackBerry Workspaces audit or authentication logs for patterns of multiple sequential login attempts from the same source, particularly those resulting in access to different user workspaces.Affected if Logs show multiple sequential login requests from a single session resulting in access to different user accounts
If BlackBerry Workspaces Server is installed with session management enabled and audit logs reveal patterns of single sessions accessing multiple user workspaces, the environment is likely affected by CVE-2017-9370.
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 dataApply vendor-provided patch for CVE-2017-9370; until patched, implement aggressive session invalidation policies, enable detailed audit logging of login events, and monitor for anomalous cross-user access patterns.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9370 — 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-2017-9370 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