CVE-2016-2205
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 · uneditedDirectory traversal vulnerability in the file-download configuration file in the management console in Symantec Workspace Streaming (SWS) 7.5.x before 7.5 SP1 HF9 and 7.6.0 before 7.6 HF5 and Symantec Workspace Virtualization (SWV) 7.5.x before 7.5 SP1 HF9 and 7.6.0 before 7.6 HF5 allows remote authenticated users to read unspecified application files via unknown vectors.
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 · high confidenceDirectory traversal vulnerability in the file-download configuration component of the management console in Symantec Workspace Streaming (SWS) and Symantec Workspace Virtualization (SWV) allows remote authenticated users to read arbitrary application files by manipulating file paths.
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= 7.5.0= 7.6.0= 7.5.0= 7.6.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/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 installed productCheck installed programs on the Windows system for 'Symantec Workspace Streaming' or 'Symantec Workspace Virtualization'. Look in Add/Remove Programs or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing these product names.Affected if Either SWS or SWV is installed
-
Determine installed versionCheck the version of the installed product. For SWS, examine the file version of StreamProxy.exe or check registry keys under HKLM\SOFTWARE\Symantec\Workspace Streaming. For SWV, check the version of SWVService.exe or similar binaries.Affected if Version is exactly 7.5.0 or 7.6.0
-
Verify management console is accessibleCheck if the management console web interface is reachable. By default this runs on ports 8080 or 8443. Use netstat or check for listening services on these ports. Also verify if the console is exposed to network access rather than localhost only.Affected if Management console is network-accessible and accepts authenticated connections
-
Confirm file-download configuration component is in useThe vulnerability exists in the file-download configuration component of the management console. Check if this feature is accessible to authenticated users by logging into the console and navigating to the file-download or download configuration areas.Affected if Authenticated users can access the file-download configuration interface
User is affected if they have SWS or SWV version 7.5.0 or 7.6.0 installed with the management console network-accessible to authenticated users.
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 the vendor-supplied hotfixes: SWS and SWV 7.5.x should upgrade to 7.5 SP1 HF9, and 7.6.0 should upgrade to 7.6 HF5. Additionally, restrict access to the management console to only trusted authenticated users as a compensating control.
- 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-2016-2205 — 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-2016-2205 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