Results 1 to 9 of 9

Thread: WMF exploit can infect XP SP2 machines (0-day virus)

  1. #1
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber

    Exclamation WMF exploit can infect XP SP2 machines (0-day virus)

    Microsoft Security Advisory

    F-Secure's weblog has some details of a "0-day" exploit involving the handling of WMF (Windows metafiles) files that can allow remote code execution on fully-patched Windows XP SP2 machines.

    There have been a handful of detected variants of this type of exploit already, I would recommend NOT visiting the sites mentioned on F-Secure "out of curiosity", and bear in mind that it is typical for XXX, warez, cracks & serials sites to be teeming with viruses, trojans, malicious javascript and a host of remote code execution attempting code.

    I think so far it looks like this has been used to drop spyware on machines, but it could be used to deploy viruses, trojans or rootkits.

    Don't be logged in as an administrator when using your machine.
    Don't go browsing "those kinds of sites".
    Keep your eyes peeled for a patch (I'll update as I get more information).


    Edit:
    Updated to add MS advisory
    Last edited by Paul Adams; 29-12-2005 at 06:01 PM.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  2. #2
    Senior Member
    Join Date
    Aug 2004
    Location
    W Yorkshire
    Posts
    5,691
    Thanks
    85
    Thanked
    15 times in 13 posts
    • XA04's system
      • Motherboard:
      • MSI X570-A Pro
      • CPU:
      • AMD Ryzen 5 3600
      • Memory:
      • Corsair 2x 8gb DDR 4 3200
      • Storage:
      • 1TB Serpent M.2 SSD & 4TB HDD
      • Graphics card(s):
      • Palit RTX 2060
      • PSU:
      • Antec Truepower 650W
      • Case:
      • Fractcal Meshify C
      • Operating System:
      • Windows 10
      • Monitor(s):
      • iiyama 34" Curved UWQHD
      • Internet:
      • Virgin 100mb Fibre
    They also list the REGSVR32 workaround. It's a good idea to use this while waiting for a patch. To quote Microsoft's bulletin:

    Un-register the Windows Picture and Fax Viewer (Shimgvw.dll)

    1. Click Start, click Run, type "regsvr32 -u %windir%\system32\shimgvw.dll"
    (without the quotation marks), and then click OK.

    2. A dialog box appears to confirm that the un-registration process has succeeded.
    Click OK to close the dialog box.

    Impact of Workaround: The Windows Picture and Fax Viewer will no longer be started
    when users click on a link to an image type that is associated with the Windows Picture and Fax Viewer.

    To undo this change, re-register Shimgvw.dll by following the above steps.
    Replace the text in Step 1 with “regsvr32 %windir%\system32\shimgvw.dll” (without the quotation marks).
    Isn't it IE that just uses that?

  3. #3
    Senile Member
    Join Date
    Dec 2003
    Posts
    442
    Thanks
    3
    Thanked
    0 times in 0 posts
    This page lists mozilla as being affected.

    http://www.kb.cert.org/vuls/id/181038

    Its windows itself that is vulnerable I guess.

  4. #4
    Senior Member
    Join Date
    Apr 2005
    Posts
    2,536
    Thanks
    15
    Thanked
    4 times in 3 posts
    Note, too, that US-CERT (http://www.kb.cert.org/vuls/id/181038) says the following:

    Remapping Windows Metafile files to open a program other than the default Windows Picture and Fax Viewer may prevent exploitation via some attack vectors.


    Trouble is, the site also says:

    Please be aware we have confirmed that filtering based just on the WMF or EMF file extensions or MIME type application/x-msMetafile will not block all known attack vectors for this vulnerability. Filter mechanisms should be looking for any file that Microsoft Windows recognizes as a Windows Metafile by virtue of its file header.



    Bob

  5. #5
    Senior Member
    Join Date
    Nov 2005
    Location
    Southampton, UK
    Posts
    253
    Thanks
    1
    Thanked
    2 times in 2 posts
    • divinemadness's system
      • Motherboard:
      • Gigabyte EP45-UD3L
      • CPU:
      • Q9550 @3.4GHz
      • Memory:
      • 4GB Corsair DDR2 PC2-6400
      • Storage:
      • 640GB WD Caviar Blue
      • Graphics card(s):
      • 896MB XFX GTX260 55nm
      • PSU:
      • Corsair TX650
      • Case:
      • CoolerMaster CM690
      • Operating System:
      • Windows 7
      • Monitor(s):
      • Samsung 2032mw
      • Internet:
      • O2 8Mb
    I had one of these try and download last night whilst 'perusing' google images

  6. #6
    Senior Member
    Join Date
    Aug 2004
    Location
    W Yorkshire
    Posts
    5,691
    Thanks
    85
    Thanked
    15 times in 13 posts
    • XA04's system
      • Motherboard:
      • MSI X570-A Pro
      • CPU:
      • AMD Ryzen 5 3600
      • Memory:
      • Corsair 2x 8gb DDR 4 3200
      • Storage:
      • 1TB Serpent M.2 SSD & 4TB HDD
      • Graphics card(s):
      • Palit RTX 2060
      • PSU:
      • Antec Truepower 650W
      • Case:
      • Fractcal Meshify C
      • Operating System:
      • Windows 10
      • Monitor(s):
      • iiyama 34" Curved UWQHD
      • Internet:
      • Virgin 100mb Fibre
    So if by default you told Windows to open all image files with Photoshop for example - it would be less of a risk?

  7. #7
    Senior Member Tobeman's Avatar
    Join Date
    Apr 2005
    Location
    IN YOUR FRIDGE, AWPIN' YOUR NOOBS
    Posts
    1,823
    Thanks
    34
    Thanked
    11 times in 11 posts
    x64 machines at risk?

  8. #8
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Not sure what else (if anything) uses Windows metafile data, so using another graphics product might not make any difference.
    Probably best to unregister that DLL for now.

    Unsure if XP x64 is affected, I don't have my 64-bit machine here to test it inside a virtual machine unfortunately.
    AFAIK there aren't any 64-bit rootkits so that's one less risk (maybe keyloggers too), but WOW64 means that the other types of autorunning crap and desktop/search/homepage altering junk would still be a risk.

    Seriously, not running as an administrator is one of the best ways to avoid most of these kinds of issues (that don't involve escalation of privileges through a hole).
    You can still easily use "Run As" to launch a specific app (or installer) to perform admin tasks when you need, but the risk associated with running a console session as Administrator is way too high.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

  9. #9
    Ex-MSFT Paul Adams's Avatar
    Join Date
    Jul 2003
    Location
    %systemroot%
    Posts
    1,926
    Thanks
    29
    Thanked
    77 times in 59 posts
    • Paul Adams's system
      • Motherboard:
      • Asus Maximus VIII
      • CPU:
      • Intel Core i7-6700K
      • Memory:
      • 16GB
      • Storage:
      • 2x250GB SSD / 500GB SSD / 2TB HDD
      • Graphics card(s):
      • nVidia GeForce GTX1080
      • Operating System:
      • Windows 10 x64 Pro
      • Monitor(s):
      • Philips 40" 4K
      • Internet:
      • 500Mbps fiber
    Last edited by Paul Adams; 29-12-2005 at 06:01 PM.
    ~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
    PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
    Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •