Vulnerability Note VU#987118

Microsoft Virtual PC for Mac insecurely handles temporary file

Original Release date: 24 Feb 2004 | Last revised: 04 Mar 2004

Overview

A component program of Microsoft Virtual PC for Mac uses an insecure method for handling a temporary file. This could allow an attacker with local system access to gain elevated privileges.

Description

Microsoft Virtual PC for Mac is a product that allows users of the Apple MacOS X operating system to simulate a PC computer in software. A component program (VirtualPC_Services) fails to check for dangerous conditions prior to creation of a specific temporary file (/tmp/VPCServices_Log) during its normal operation. As a result, an attacker could create a symbolic link that would cause the contents of another file to be overwritten or a new file to be created. Since the VirtualPC_Services component that exposes the vulnerability runs with increased privileges, the attacker's file would be written with system privileges.

Impact

An attacker with local access may be able to overwrite or create any file on the system. Depending on which file was created or overwritten, this could allow the attacker to gain elevated privileges or a cause a denial-of-service condition on the system.

Solution

Apply a patch from the vendor

Apply the patch (835150) referenced in Microsoft Security Bulletin MS04-005.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Microsoft CorporationAffected-24 Feb 2004
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This vulnerability was reported by George Gal of @stake .

This document was written by Damon Morda and Chad Dougherty based on information provided by @stake.

Other Information

  • CVE IDs: CAN-2004-0115
  • Date Public: 10 Feb 2004
  • Date First Published: 24 Feb 2004
  • Date Last Updated: 04 Mar 2004
  • Severity Metric: 3.67
  • Document Revision: 23

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.