The information has been provided by Microsoft Security Bulletin MS07-067.
The original article can be found at:
* Windows XP Service Pack 2
* Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2
* Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2
* Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2
* Microsoft Windows 2000 Service Pack 4
* Windows Server 2003 for Itanium-based Systems
* Windows Vista
* Windows Vista x64 Edition
Macrovision Driver Vulnerability - CVE-2007-5587:
A local elevation of privilege vulnerability exists in the way that the Macrovision driver incorrectly handles configuration parameters. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-5587.
Mitigating Factors for Macrovision Driver Vulnerability - CVE-2007-5587:
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
* An attacker must convince a user to run an executable or must have valid logon credentials to exploit this vulnerability. This is a local elevation of privilege vulnerability. The exploit for this vulnerability can not be done remotely.
* Microsoft Windows 2000 Service Pack 4 is not affected.
* Windows Vista is not affected.
Workarounds for Macrovision Driver Vulnerability - CVE-2007-5587:
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
* Disable the secdrv.sys driver
Disabling the secdrv.sys driver in the system registry key helps protect affected systems from attempts to exploit this vulnerability.
Note: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.
1. Click Start, click Run, type regedit and then click OK.
2. Expand HKEY_LOCAL_MACHINE.
3. Expand SYSTEM, expand CurrentControlSet, and then expand Services.
4. Click Secdrv.
5. Click the File menu and select Export.
6. To backup the registry before your edit it, left click on File menu, select Export... In the Export Registry File dialog box, type Secdrv_configuration_backup.reg and select Save.
7. Double-click the value named Start, and change the Value data: field to 4.
8. Click OK.
9. Click Start, click All Programs, click Accessories, and click Command Prompt.
10. Run the following command at a command prompt:
Sc stop secdrv
* Managed Deployment Script
1. Make a backup copy of the registry keys from a managed deployment script using the following command:
regedit /e Secdrv_configuration_backup.reg HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Secdrv
2. Save the following to a file with a .REG extension (e.g. Disable_Secdrv.reg):
Windows Registry Editor Version 5.00
3. Run the registry script created in Step 2 on the target machine with the following command:
Regedit /s Disable_Secdrv.reg
4. Click Start, click All Programs, click Accessories, and click Command Prompt.
5. Run the following command at a command prompt:
sc stop secdrv
Impact of workaround. Programs that require this driver will not run.
FAQ for Macrovision Driver Vulnerability - CVE-2007-5587:
What is the scope of the vulnerability?
This is a local elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.
What causes the vulnerability?
The Macrovision driver incorrectly handles configuration parameters.
What is secdrv.sys?
The driver, secdrv.sys, is used by games which use Macrovision SafeDisc. The driver validates the authenticity of games that are protected with SafeDisc and prohibits unauthorized copies of such games to play on Windows. The secdrv.sys is included with Microsoft Windows XP, Windows Server 2003, and Windows Vista to increase compatibility of the games on Windows. Without the driver, games with SafeDisc protection would be unable to play on Windows. SafeDisc remains inactive until invoked by a game for authorization to play on Windows.
What might an attacker use the vulnerability to do?
A local attacker could successfully exploit this vulnerability to gain full control of an affected system.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, the attacker must have valid credentials to log on to the system, which would allow the attacker to run a specially crafted application that could exploit the vulnerability and gain full control of the affected system.
Does the update offered by Macrovision address the same vulnerability?
Version 126.96.36.199 of secdrv.sys driver is offered by Macrovision and Microsoft for all affected versions of Windows. Only build times differ between the Macrovision and Microsoft updates for the secdrv.sys driver.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number CVE-2007-5587. This vulnerability was first described in Microsoft Security Advisory 944653.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.