Revision History 2/21/2008 - updated unaffected product list
|Remote Access||Yes, Local network access normally required|
|Exploit publicly available||No|
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) Not Affected
|Veritas Volume Manager||3.1|
|Veritas Storage Foundation for Windows||4.1, 4.1RP1|
|Veritas Storage Foundation for Windows||4.2, 4.2RP1, 4.2RP2|
|Veritas Storage Foundation for Windows||4.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 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:
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
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.
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.
REPORTING VULNERABILITIES TO SYMANTEC
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 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 firstname.lastname@example.org
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 email@example.com
The Symantec Software Security PGP key can be found at the following location:
COPYRIGHT (C) 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 Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org