SYM07-009,Symantec Storage Foundation for Windows Volume Manager: Authentication Bypass and Potential Code Execution in Scheduler Service
Symantec Security Advisory
http://www.symantec.com/avcenter/security/Content/2007.06.01.html
SYM07-009
1 June, 2007
Symantec Storage Foundation for Windows Volume Manager: Authentication Bypass
and Potential Code Execution in Scheduler Service
Revision History
None
Severity
Medium
Remote Access Yes, Local network access required
Local Access No
Authentication Required No
Exploit publicly available No
Overview
An authentication bypass, remote code execution vulnerability has been
identified and resolved in the Symantec Storage Foundation for Windows v5.0
Volume Manager Scheduler Service. Successful exploitation could result in
potential compromise of the targeted system.
Product(s) Affected
Product Version Solution(s)
Symantec Storage Foundation
for Windows 5.0 http://support.veritas.com/docs/288627
Product(s) Not Affected
Product Version
Symantec Storage Foundation for Windows 3.1
Symantec Storage Foundation for Windows 4.1, 4.1RP1
Symantec Storage Foundation for Windows 4.2, 4.2RP1, 4.2RP2
Details
3Com?s Zero Day Initiative, notified Symantec of an authentication bypass and
arbitrary code execution vulnerability discovered in the Symantec Storage
Foundation for Windows Scheduler Service, VxSchedService.exe. The Scheduler
Service server, initially introduced in Symantec Storage Foundation for Windows
v5.0, listens for incoming scheduling messages from client systems. An
attacker with network access who could successfully connect directly to the
Scheduler Service socket could bypass the built-in authentication in the
management console. By properly manipulating this vector, the attacker has the
potential to possibly add arbitrary commands to the registry that could be
executed during normal scheduled runs.
This vulnerability, if successfully exploited, would most likely be initiated
by a malicious user authenticated on the local network since the affected
service port should not normally be available to other than authorized network
systems. Any potentially successful attack by a non-authorized remote attacker
would most likely be a scenario of enticing an authorized user to run or allow
to run malicious code that might successfully exploit this issue.
Symantec Response
Symantec takes the security of our products and our customers very seriously.
Symantec engineers have verified and corrected this issue in Symantec?s Storage
Foundation for Windows 5.0.
Updates are available for 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.
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://support.veritas.com/docs/288627
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-2279 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 3Com/ZDI for reporting this issue and for
providing full coordination while Symantec resolved it.