WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
SYM08-004
20 February, 2008
Veritas Storage Foundation for Windows by Symantec: Denial of Service in Scheduler Service

Revision History
2/21/2008 - updated unaffected product list

Severity
Low

Remote AccessYes, Local network access normally required
Local AccessNo
Authentication RequiredNo
Exploit publicly availableNo

Overview
A Denial of Service (DoS) has been identified and resolved in the Veritas Storage Foundation for Windows v5.0 Volume Manager Scheduler Service. Successful exploitation results in a service halt requiring manual intervention by an administrator to restart the Scheduler Service.

Product(s) Affected
ProductVersionPlatformSolution(s)
Veritas Storage Foundation for Windows5.0Win2k, Win2003 32-bithttp://entsupport.symantec.com/docs/297166
Veritas Storage Foundation for Windows5.0Win2k, Win2003 64-bithttp://entsupport.symantec.com/docs/297167

Product(s) Not Affected
ProductVersion
Veritas Volume Manager3.1
Veritas Storage Foundation for Windows4.1, 4.1RP1
Veritas Storage Foundation for Windows4.2, 4.2RP1, 4.2RP2
Veritas Storage Foundation for Windows4.3, 4.2MP1, 4.2MP2

Details
iDefense Labs, notified Symantec of a DoS vulnerability discovered in the Veritas Storage Foundation for Windows Scheduler Service, VxSchedService.exe. The Scheduler Service, newly introduced in Symantecís Veritas Storage Foundation for Windows v5.0, listens for incoming scheduling messages from client systems. An attacker with network access could successfully pass malformed packets to the service causing it to run out of processing memory. The service halt requires manual intervention by an administrator to restart the service and re-enable scheduling activity.

This vulnerability, if successfully exploited, would most likely be initiated by a malicious user authenticated on or with access to the local network since the affected service port should not normally be available externally to the authorized network.

Symantec Response
Symantec takes the security of our products and our customers very seriously. Symantec engineers have verified and provided a fix for this issue in Symantecís Veritas Storage Foundation for Windows 5.0.

Symantec recommends customers apply the latest product update to enhance their security posture and protect against potential security threats of this nature.

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

Additional information on patches for affected product/versions above is available from the following location:
http://entsupport.symantec.com/docs/297329

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

Reference
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate CVE-2007-4516 to this issue.
This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.
SecurityFocus has assigned Bugtraq ID BID 27440 to this issue for inclusion in the SecurityFocus vulnerability database.

Credit
Symantec would like to thank iDefense Labs for reporting this issue and for providing full coordination while Symantec resolved it.


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.

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


Copyright (c) 2009 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.

Disclaimer
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.


Last modified on: Thursday, 21-Feb-08 21:26:25