[ WinXP ] Important update

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Schadenfroh provided links to the finalized update patches by Microsoft :thumbsup: You can also get them by using the Microsoft Update site or by the Automatic Updates feature of Windows.







Update for those interested: I see from this blog entry that Microsoft is testing the updated driver so they can eventually release it via the usual methods as a security patch.

As the vulnerable driver is included with Windows XP and Windows Server 2003 we wanted to make sure you knew that we are working with Macrovision to test the Macrovision update for deployment using Microsoft?s security update process. Once the update has gone through the Microsoft security update testing process, completed deployment testing and is ready for release, Microsoft will release it to customers as part of the Microsoft security update process.

So those wanting to fix this vulnerability right away should still get the patch from Macrovision. See below.


There is a notable security vulnerability in a Macrovision SafeDisc driver which shipped with WinXP and Windows Server 2003. It appears that it could be used by means of Trojans or exploits to attack your computer.

Macrovision's download page for the fix Download the Zip file, extract the contents, right-click the .INF file and choose Install.

Microsoft's security advisory on the topic They report the vulnerability is being exploited in the wild.


The bad guys exploit all sorts of stuff, including third-party apps like Acrobat Reader, QuickTime, Sun Java, WinZip, WinAmp, Yahoo Messenger, etc etc etc, so I'll mention the useful Secunia checkup tools that help you eliminate those weaknesses:

Secunia online checkup, which is Java-driven

Secunia's installable version (not Vista-compatible yet)
 

SilentRunning

Golden Member
Aug 8, 2001
1,493
0
76
From Security advisory:
Mitigating Factors

Microsoft Vista is not vulnerable to this issue.

An attacker must have logon permissions to the operating system to exploit this vulnerability.

&

What might an attacker use this driver to do?
An attacker with local access to a system could successfully exploit this vulnerability to gain elevation of privilege on an affected system.

Why does this make me think macrovision just wants to push an update onto users as a security risk.

 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
An attacker must have logon permissions to the operating system to exploit this vulnerability.

And when you log onto your system to use it... yeah. An exploit or trojan could conceivably make you into the locally-logged-on attacker, basically.
 

MustISO

Lifer
Oct 9, 1999
11,927
12
81
Why does this make me think macrovision just wants to push an update onto users as a security risk.

I was thinking the same thing. I do believe that there is a security risk with the driver but it would not suprise me if the "fix" comes with a rootkit or something worse.
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Having installed the fix on a couple WinXP computers equipped with KAV7 and not gotten any rootkit warnings, I think maybe you have your tinfoil hat on a bit too tight :D;)
 

SilentRunning

Golden Member
Aug 8, 2001
1,493
0
76
Originally posted by: mechBgon
Having installed the fix on a couple WinXP computers equipped with KAV7 and not gotten any rootkit warnings, I think maybe you have your tinfoil hat on a bit too tight :D;)

I wasn't thinking rootkit so much as an update to macrovision to try to prevent current ways of circumventing it (more DRM.)

Calling it a security issue would push it on more systems than calling it an update to prevent piracy.

 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Originally posted by: SilentRunning
Originally posted by: mechBgon
Having installed the fix on a couple WinXP computers equipped with KAV7 and not gotten any rootkit warnings, I think maybe you have your tinfoil hat on a bit too tight :D;)

I wasn't thinking rootkit so much as an update to macrovision to try to prevent current ways of circumventing it (more DRM.)

Calling it a security issue would push it on more systems than calling it an update to prevent piracy.

As an alternative, I suppose you could rename the insecure driver file so it doesn't get used by anything, good or bad.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,571
10,206
126
I'm surprised to hear that XP ships with a SafeDisc driver OOB, I thought that it was normally installed once you installed some DRMed game or something.