CVE-2017-9368
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 vulnerability in the BlackBerry Workspaces Server could result in an attacker gaining access to source code for server-side applications by crafting a request for specific files.
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 confidenceThe BlackBerry Workspaces Server contains an information disclosure vulnerability that allows unauthenticated attackers to request and obtain source code for server-side applications by crafting specific file requests.
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= 5.5.0= 5.5.1= 5.5.2= 5.5.3= 5.5.4= 5.5.5= 5.5.6= 5.5.7= 5.5.8= 5.5.9= 5.6.0= 5.6.1<= 1.11.2CVSS 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 BlackBerry Workspaces versionCheck the server management console, about page, or installation documentation for the exact version number of BlackBerry Workspaces Server (Vapp or Appliance X)Affected if The installed version is 5.5.0, 5.5.1, 5.5.2, 5.5.3, 5.5.4, 5.5.5, 5.5.6, 5.5.7, 5.5.8, 5.5.9, 5.6.0, 5.6.1 (Vapp) or 1.11.2 or lower (Appliance X)
-
Confirm product typeDetermine whether the deployment is Vapp (virtual appliance) or Appliance X, as version ranges differ between these product linesAffected if The product is either Vapp in the listed version range or Appliance X version 1.11.2 or lower
-
Verify server network accessibilityConfirm the BlackBerry Workspaces Server is reachable over the network (HTTP/HTTPS ports) from untrusted networksAffected if The server is exposed to network access without proper firewall restrictions, allowing unauthenticated attackers to reach it
-
Check for source code exposure responseCompare your installed version to the affected ranges; if within affected versions and network-accessible, the server could respond to crafted file requests that return application source codeAffected if The server version falls within affected ranges AND the server is network-accessible to unauthenticated users
You are affected if your BlackBerry Workspaces Server is version 5.5.0-5.6.1 (Vapp) or <=1.11.2 (Appliance X) and is accessible to unauthenticated network attackers.
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 dataRestrict access to source code files on the server, implement proper access controls, and apply vendor patches if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9368 — 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-9368 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