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

Security Advisories Relating to Symantec Products - Veritas Storage Foundation for Windows Volume Manager Scheduler Service for Windows Security Update Circumvention

SYM08-015

August 14, 2008

Revision History

None

Severity

Medium

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

Overview

It is possible to circumvent the security patch that resolved a previously identified authentication bypass, remote code execution vulnerability in the Veritas Storage Foundation for Windows v5.0 Volume Manager Scheduler Service. Successful exploitation could result in potential compromise of the targeted system.

Affected Products

ProductVersionSolution(s)
Veritas Storage Foundation for Windows5.0, 5.0 RP1a, 5.1http://entsupport.symantec.com/docs/306386

Note: Only those versions identified above are affected by this issue.

Details

3Com’s Zero Day Initiative, notified Symantec of a vector that can allow a malicious user to circumvent the security update for an authentication bypass vulnerability previously reported in the Veritas Storage Foundation for Windows Scheduler Service,
http://www.symantec.com/avcenter/security/Content/2007.06.01.html.

The Scheduler Service server, introduced in Veritas Storage Foundation for Windows v5.0, listens for incoming scheduling messages from client systems. An attacker with network access who could connect directly to the Scheduler Service socket could bypass the security update to the previously reported issue. By properly manipulating this vector, the attacker has the potential to add arbitrary commands to the registry that, if properly constructed, would be executed on the targeted system during normal scheduled runs.

Symantec Response

Symantec engineers have verified and resolved this issue in the Veritas Storage Foundation for Windows versions and builds identified above.

Symantec recommends customers apply the latest product update available for their supported product versions 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.

The patches listed above for affected product/version are available from the following location:
http://entsupport.symantec.com/docs/306386

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.

Credit

Symantec would like to thank Tenable Security working through 3Com ZDI for reporting this issue and for providing coordination while Symantec resolved it.

References

SecurityFocus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID), 30596 to this issue for inclusion in the SecurityFocus vulnerability data base. The BID can be found at http://www.securityfocus.com/bid/30596

This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. A CVE Candidate name has be requested from the Common Vulnerabilities and Exposures (CVE) initiative for this issue. This advisory will be revised accordingly upon receipt of the CVE Candidate name.
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.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product 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 Product Security PGP key can be found at the location below.
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.

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 Product Security. 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 Product Security, 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.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: August 14, 2008
Security Response Blog
The State of Spam