Visit our newest sister site!
Hundreds of free aircraft flight manuals
Civilian • Historical • Military • Declassified • FREE!

TUCoPS :: Security App Flaws :: tb11169.htm

Symantec Reporting Server elevation of privilege
SYM07-012 Symantec Reporting Server elevation of privilege
SYM07-012 Symantec Reporting Server elevation of privilege

SYM07-012 Symantec Reporting Server Elevation of Privilege

June 5, 2007 

Risk Impact

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

Files created by a Reporting Server may be accessible to an unauthorized user.    

Affected Products 
Reporting,  up to the solution SAV 10.1 MR6  build 6000 (  or later

Reporting or later=09
Reporting is not available as a stand-alone application, but is distributed with Symantec AntiVirus and Symantec Client Security.  Reporting  or later is available with the following products
SAV 10.1 MR6  build 6000 (  or later
SCS 3.1 MR6 build 6000 ( or later


Symantec Reporting Server is an optional web application within the Symantec System Center console that can be used to be used to create reports about Symantec Client Security and Symantec AntiVirus products in an enterprise network.

Symantec was notified that a file created in the process of exporting data from Reporting Server could be potentially be manipulated by an unauthorized user to create a malicious executable file.   An attacker could then execute the file, potentially gaining access to the server in the context of the web server user.  

Symantec Response

Symantec engineers verified that the issue exists in Reporting Server included with the product versions listed above.   The error occurred due to the improper initialization of a variable, and updates have been released to correct the problem.  

This vulnerability affects only systems on which the Reporting Server program is installed. Individual client systems are not affected.

Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.  However, we recommend that customers update Reporting Server immediately to protect against possible attempts to exploit this issue. 

Mitigation and best practices

- Uninstall Reporting Server if it is not being used
 - Symantec Client Security Console (SCS Console) and the Reporting Server interface should be restricted to trusted access only.  
 - Ensure that the SCS Console and Reporting Server interface are never visible external to the network.  This greatly reduces opportunities for unauthorized remote access. 
- User accounts for Reporting Server should be unique, and different from the user=92s network login account.  
- Delete exported data files which are no longer needed.  

Symantec would like to thank Ertunga Arsal of Tech Data GmbH & Co. OHG for reporting this issue, and coordinating with us on the response.  

This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (, which standardizes names for security problems. The CVE initiative has assigned CVE-2007-3021 to this issue 

Hash: SHA256

Symantec Product Security Team

Symantec takes the security and proper functionality of its products very
seriously. As founding members of the 
Organization for Internet Safety (OISafety), Symantec follows the
principles of responsible disclosure. Symantec also 
subscribes to the vulnerability guidelines outlined by the National
Infrastructure Advisory Council (NIAC). Please contact if you feel you have discovered a potential or actual 
security issue with a Symantec product. 
Copyright (c) 2007 by Symantec Corp.

Version: PGP Desktop 9.0.6 (Build 6060)


TUCoPS is optimized to look best in Firefox® on a widescreen monitor (1440x900 or better).
Site design & layout copyright © 1986-2015 AOH