Zero Day Flaw in Windows Media Player

Microsoft sure has a lot of running work to do. Just a day after a Zero Day flaw was detected in Word, a new flaw has been detected in Windows Media Player.

There is a detailed explanation for it as below:

The Windows Media Player library WMVCORE.DLL contains a potentially exploitable heap buffer overflow in its handling of “REF HREF” URLs within ASX files. If the URL contains an unrecognized protocol (only “file”, “ftp”, “http”, “https”, “mms”, “mmst”, “mmsu”, “rtsp”, “rtspt”, and “rtspu” appear to be recognized), the function at 7D7A8F27 in WMVCORE.DLL version 9.0.0.3250, and at 086E586E in WMVCORE.DLL version 10.0.0.3802, will create a copy of the string in which the protocol is replaced with “mms”. A heap buffer is allocated, the string “mms” is copied into it, and then everything after and including “://” in the “REF HREF” URL is concatenated using wcsncat.

Unfortunately, the heap buffer for the new “mms” URL is allocated to the size of the “REF HREF” URL, and even more unfortunately, the length of the input string being passed to wcsncat is supplied as the character count, effectively causing wcsncat to behave identically to wcscat. As a result, a two- or four-byte heap overflow is possible if the “REF HREF” URL features a protocol shorter than three characters (the length of “mms”).

Single-letter protocols (such as “a://”) are rejected, but this restriction can be circumvented by encoding the protocol (“%61://”), thereby making a four-byte overflow possible.

As of now, there are no reports about any known exploits of this.

Solution

Disable Windows Media Player from auto-opening .ASX files by going to Tools » Folder Options » File Types – Set “ASX” to something other than Windows Media Player (default).

Advertisements

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.