WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
Symantec Security Advisory
July 27, 2007
Symantec Discovery Insecure File Permissions

Revision History


Remote AccessLocal network access required
Local AccessYes
Authentication RequiredYes
Exploit publicly availableNo

Insecure default directory and file permissions may allow local users to gain escalated privileges.

Affected Products
Symantec Discovery 6.X All

Due to insecure default directory and file permissions, it is possible for local, non-privileged users to potentially replace key Symantec Discovery components with malicious content.

Symantec response
On July 23, 2007 security firm Secunia issued a security advisory relating to insecure file permissions on Symantec Discovery. This advisory relates to the default file permissions set at installation on the Symantec Discovery server.

The Symantec Discovery product was designed by its 3rd-Party vendor, Centennial Software, such that anyone with access to the Discovery server should have the ability to run the Discovery Control Center. Symantec recommends that server access be restricted to administrators only. For most customers, administrative access only is allowed to the Discovery server. These customers are not affected by this issue. For customers who would like to implement a higher level of security than what is already present within their implementation, we recommend more stringent file based permissions on the directory be set to limit access from unauthorized local users. Please contact your Symantec Support representative for any required assistance.

Best Practices
As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Restrict remote access, if required, to trusted/authorized systems only.
  • Run under the principle of least privilege where possible to limit the impact of exploit by threats.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
  • Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities

Secunia Advisory: http://secunia.com/advisories/25374/

Symantec Support Knowledge base article:

SecurityFocus (http://www.securityfocus.com) has assigned Bugtraq ID (BID) 25000 to this issue.

This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2007-2950 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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).

Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the end of this message.

Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

PDF Symantec Vulnerability Response Policy PGP Symantec Product Vulnerability Management PGP Key

Copyright © by Symantec Corp.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.

Initial Post on: Friday, 27-Jul-07 10:30:00
Last modified on: Friday, 27-Jul-07 10:39:29