WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
SYM07-010
June 1, 2007
Symantec Storage Foundation Solutions Suites: Veritas Volume Replicator, Denial of Service in Veritas Administrative Service

Revision History
None

Risk Impact
Low

Remote AccessNetwork access or authorized user interaction required
Local AccessNo
Authentication RequiredNo
Exploit publicly availableNo

Overview
A Denial of Service (DoS) vulnerability has been identified and resolved in the Symantec Veritas Volume Replicator (VVR) option, specifically in the administrative service. Symantec's VVR ships as a licensable option with Symantec's Storage Foundation Solutions Suites. If the VVR option is installed, successful implementation of a DoS attack could terminate the service. In some circumstances, resource exhaustion as a result of the DoS could potentially lead to additional system degradation.

Product(s) Affected
ProductVersionPlatform(s)Solution(s)
Symantec VeritasVolume Replicator for Windows 3.1 Win2k http://support.veritas.com/docs/286807
4.1, 4.1RP1 Win2k, Win2003 32-bit
4.2, 4.2RP1, 4.2RP2 Win2k, Win2003 32-bit
4.3, 4.3MP1 Win2k, Win2003 32-bit, 64-bit
Symantec Veritas Volume Replicator for Unix 3.5 HP-UX http://support.veritas.com/docs/286807
4.0 AIX
4.1 Solaris, Solaris Opteron, HP-UX, Linux
5.0 Solaris, HP-UX, Linux, AIX

Details
iDefense notified Symantec of a DoS vulnerability identified in the Symantec VVR administrative service. The DoS was caused by failure to properly validate incoming data passed to the VVR service. A specifically crafted packet passed to the vulnerable service could result in the VVR administrative service terminating unexpectedly. The VVR administration service will require a restart. This type of attack could also potentially lead to degraded application functions on the targeted system or to the overall system due to excessive CPU resource consumption during memory allocation attempts prior to VVR administrative service termination.

This DoS, if successfully exploited, would more likely be the result of an internal attack by an authorized malicious user on the network since network access would normally be required to reach the affected service port. Any potentially successful attack by a non-authorized remote attacker would most likely be a scenario of interactive user involvement by enticing a user to run or allow malicious code to be run that could successfully impact a vulnerable system.

Symantec Response
Symantec takes the security of our products and our customers very seriously. Symantec engineers have verified and corrected these issues in all currently supported vulnerable versions of Symantec's Veritas Volume Replicator.

Updates are available for all supported products. 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.

To determine if the VVR option is installed on a system

Symantec Veritas Storage Foundation Suite for Windows:

  1. from a command prompt, run the command "vxrvg.exe", as system or domain administrator
  2. if the command is NOT found, the VVR option is not installed and the system is not vulnerable
  3. if the command IS found, the system is vulnerable and the appropriate solution should be applied

Symantec Veritas Storage Foundation Suite for *nix platforms
  1. run the command: /sbin/vxlictest -n "VERITAS Volume Manager" -f "VVR" as root
  2. if the license is NOT found, the VVR option is not installed and the system is not vulnerable
  3. if the license IS found, the system is vulnerable and the appropriate solution should be applied

Note: Should a customer determine at a later date to install the VVR option, the appropriate updates must be applied.

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

The location for patches listed above for affected products can be found in the following:
http://support.veritas.com/docs/286807

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

CVE
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate CVE-2007-1593 to this issue.

This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.

Credit:
Symantec would like to thank iDefense for reporting these issues and for providing full coordination while Symantec resolved them.


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.


Initial Post on: Friday, 01-Jun-07 13:00:00
Last modified on: Friday, 01-Jun-07 20:47:54