Microsoft patch for WMF flaw to be released Jan 10


Recommended Posts

Microsoft Corp. said today it does not plan to release a fix for the Windows Metafile (WMF) flaw until Jan. 10, when a patch will be included as part of the company's scheduled monthly updates for January. Microsoft has completed development of a patch for the flaw and is now testing it for quality and application compatibility, the company said in an advisory updating an earlier advisory released last week. The update will be available at Microsoft's Download Center in 23 languages for all affected versions of the Windows operating system.

"Microsoft has been carefully monitoring the attempted exploitation of the WMF vulnerability since it became public last week, through its own forensic capabilities and through partnerships within the industry and law enforcement," the company said in its statement. " Although the issue is serious and malicious attacks are being attempted, Microsoft's intelligence sources indicate that the scope of the attacks are not widespread."

Source: Computer World

http://www.computerworld.com/securitytopic...html?source=x10

Lets don't get in no hurry Micorsoft...lets wait another 7 days while 1000's of people are getting infected due to a Vulnerability in your OS.

Well I guess the people who don't know about this flaw will have to depend on their antiviruses (... that are hopefully updated...).

Though I have to admit, as bad as this exploit looked, I haven't seen this around as much as other exploits yet.

:o THey should have released this on priority

And then could you imagine the yelling that the patch breaks other things, I'd wait or install the un offical patch till this one is release :cool:

I see both sides and I'm sure Microsoft does as well. This is a big gamble right here, Microsoft could release it early or 'priority' and risk breaking more stuff or Microsoft could take it a little easier and risk more computers being infected (which is the users fault for not being more careful in where they search) and release it with the proper amount of testing. Not an easy decision and I'm so glad I'm not the one having to make it :yes:

Hurmoth makes a good point but what sort of a message does this send out to customers? To me it says we where totally unprepared and until we get our self sorted you will have to look else where for a solution. Come on a 3rd party got a patch out before microsoft could.

Hurmoth makes a good point but what sort of a message does this send out to customers? To me it says we where totally unprepared and until we get our self sorted you will have to look else where for a solution. Come on a 3rd party got a patch out before microsoft could.

Personally, I don't think it sends out any message to customers. I mean think of it, how many of Microsoft's customers actually even know this threat exsists? I doubt the majority of them do, so look at it this way:

  • Microsoft currently has what maybe 1-5% infected computers out there. So:
  • If they released a patch to early because they just wanted it out there and it broke stuff you now have 10-15% customer base angry.

My point is, 1-5% customer base isn't a huge deal when looking at the big picture, but getting into double-digits could turn into a big deal. This is something you have to take into account the HUGE number of people that run Windows out there and then think of the amount of people who are actually affected by this problem and if a patch is released that breaks other stuff the larger number of people that would be affected.

It always amazes me when Microsoft is always heralded as the culprit in an attack on its software. If some people were smart enough to install & update antivirus, use firewall's, and don't do something stupid like opening up files you have no idea of what they are there wouldn't even be 10-15% infected with this now. Probably more like less then 1%.

Lol people always blaming Microsoft - they must have wanted to make software with vulnerabilities - I'm sure that's their goal. :shiftyninja:

Seems to me their doing what they should be doing - fixing the issue and making sure the fix works.

and don't do something stupid like opening up files you have no idea of what they are there wouldn't even be 10-15% infected with this now. Probably more like less then 1%.

Im not an idiot with computers but Ive always been under the false belief that when you get a email with a .exe file extension then its probably a virus.

But I always thought it was safe to open .jpg files i mean there harmless its just an image it cant run a program. oww sorry it can. This is isnt big, But has the potential to be huge.

Im not an idiot with computers but Ive always been under the false belief that when you get a email with a .exe file extension then its probably a virus.

But I always thought it was safe to open .jpg files i mean there harmless its just an image it cant run a program. oww sorry it can. This is isnt big, But has the potential to be huge.

I'm not a virus expert by no means, but if I'm not mistake no file with an extension .jpg, .gif, .png, etc. can execute a virus. Only .com, .exe, etc. can be viruses, they hide the extension as something like 'hotpr0n.jpg.exe' but you don't see the .exe.

The biggest problem is public awareness. To many times people are trashed with anti-virus, anti-spam, anti-spyware, anti-whatever. What we need is to teach, or educate, people safe-surfing. People need to know going to places to download screensavers will most likely get you viruses, spyware, adware, or whatever. People need to know that clicking "YES" to everything without reading what they're clicking "YES" to is dangerous.

Anti-whatevers isn't the answer, public awareness is.

Only .com, .exe, etc. can be viruses, they hide the extension as something like 'hotpr0n.jpg.exe' but you don't see the .exe.

Really funny I could have sworn this exploit was in .wmf files clearly not a exe or com etc

The people who get dinged by this are those who don't use anti-virus, have machines that are already infected with scumware, don't keep there machines updated and will click on anything sent to them via email.

Due to various updates from MS users using Outlook 2K and 2K3 plus Outlook Express can't fall victim to these malformed images because by default the images are not displayed in the viewer.

I think Microsoft is very wise to wait to release the patch. We aren't talking about a virus here, that spreads from infected machines, we are just talking about a vulnerability screwing some machines up. Really the only ones getting infected are the ones stupid enough to not run an antvirus, or update the one they have. I don't think Microsoft should throw an untested patch out in the wild for that, and risk breaking a whole bunch of other stuff. It would suck to be Microsoft, really, because they are damned if they do and damned if they don't.

Edited by warwagon

Really funny I could have sworn this exploit was in .wmf files clearly not a exe or com etc

You are right this exploit is in a .WMF file but all it doing is using a feature that was included that allowed the image files to contain actual code. This code would be executed via a callback in special situations and this call-back function is then being used to download the virus - which is an .exe

Really funny I could have sworn this exploit was in .wmf files clearly not a exe or com etc

Well, like I stated, I'm not an expert :p Is .WMF an executable? How can it run unless it executes and in Windows only certain extensions can execute I though.

What I find odd is that McAfee says this is a "Low Risk" & Symantec says it is a "High Risk". :rofl:

Well, like I stated, I'm not an expert :p Is .WMF an executable? How can it run unless it executes and in Windows only certain extensions can execute I though.

What I find odd is that McAfee says this is a "Low Risk" & Symantec says it is a "High Risk". :rofl:

Windows Metafiles can contain executable code (originally designed [back in the Win 3.0 days] to pause print jobs, and related stuff), someone has just found this out and is starting to hack away at it...

from teh Wiki:

According to F-Secure assessments [4], the problem lies in the design of the WMF file. Since the architecture of the file is from a previous era, features were included which allowed actual code to be executed when a WMF file was opened. This mainly dealt with cancellation of print jobs during spooling. It has also been suggested that there may be more vulnerabilities in the functions of the WMF file. Because of the large support of Metafiles in the Windows operating system, most versions of Windows are vulnerable.

Better late than never I guess :p

It only takes common sense to avoid the vulnerability. Firefox will ask you to download and run the dodgy .wmf, and other browsers probably do too. It's only IE that will automatically run the file...but IE users deserve to get exploited anyway.

Thats the thing though Hurmoth a .wmf file could be renamed to .jpg and will have the same affects in executing a .exe file from the internet.

Since my last post I've gone and rearched this. Interesting stuff, but again this still comes down to public awareness though. Who many 'normal' users open every email they get? I'd say at least the majority, which is why they need to be tought if you don't know the sender or if the email is suspecious, don't open it.

I agree hurmoth it is down to public awareness, unless you are expecting to receive an email from a friend that has the attachment happynewyear.jpg dont open it, and if you get an email from a friend that is out of context ie it doesn?t seem like them who has sent it don?t open the attachments. Basically AV is good but the best protection from internet crap is safe browsing. Hey lets make are own campaign of ?awareness? stuff this current crap in America about no videogames. Change peoples interests to safe internet use.

Since my last post I've gone and rearched this. Interesting stuff, but again this still comes down to public awareness though. Who many 'normal' users open every email they get? I'd say at least the majority, which is why they need to be tought if you don't know the sender or if the email is suspecious, don't open it.

Depends on what the vulnerability is about. This wmf thing can be (an has already be found to be) embeded in "trusted" web sites. Someone could place one of those wmf files in the neowin forums and almost every windows user would get infected.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!