1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec Workspace Streaming Potential Unauthorized Downloads


June 16, 2010

Revision History




Remote Access Yes
Local Access No
Authentication Required No
Exploit publicly available No


Symantec’s Workspace Streaming client fails to properly authenticate with the Symantec Workspace Streaming server when downloading files. This could potentially lead to unauthorized download of arbitrary code to a client system.

Products Affected

Product Version Build Platform Solution
Symantec AppStream 5.2.x All All Upgrade to SWS 6.1 and apply all available updates
Symantec Workspace Streaming 6.1.x All All 6.1 SP4


CERT identified a weakness in the Symantec Workspace Streaming application (formerly Symantec AppStream). The Symantec Workspace Streaming client does not properly authenticate with the server prior to downloading available files hosted on the server.

A malicious user could potentially establish a rogue Workspace Streaming server masquerading as an authorized server. If the server is properly configured and recognized by the client, this lack of proper authentication could possibly allow download of arbitrary files to a client system with no interaction required from the system user. This could result in successful arbitrary file download and possible execution on the client system.

Symantec Response

Symantec product engineers have developed and released a solution through Symantec's support download location as indicated. Symantec recommends all customers apply the latest available updates to protect against threats of this nature.

Symantec knows of no exploitation of or adverse customer impact from this issue.

Symantec Workspace Streaming 6.1 SP4 is currently available for update through the FileConnect -Electronic Software Distribution web site.

Best Practices

As part of normal best practices, Symantec strongly recommends a multi-layered approach to security
  • Restrict access to administration or management systems to privileged users.
  • Restrict remote access, if it is required, to trusted/authorized systems only.
  • Run under the principle of least privilege where possible to limit the impact of potential exploits.
  • Follow a multi-layered approach to security. Run both firewall and antivirus applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Users should be cautious of mysterious attachments and executables delivered via email and be cautious of browsing unknown/untrusted websites or opening unknown/untrusted URL links.


Symantec thanks Will Dormann with CERT for reporting this finding and coordinating closely with Symantec as we resolved the issue.


Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 40611 to this issue for inclusion in the Security Focus vulnerability database.

This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org). The CVE initiative has assigned CVE-2008-4389 to this issue.


Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Symantec has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC) practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact secure@symantec.com if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com.
The Symantec Software Security PGP key can be found at the following location:
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.
Last modified on: June 16, 2010
Security Response Blog
The State of Spam