Must Read: Google Glass jailbreak: Let the evil commence

Topic: Security

Microsoft issues new version of patch pulled on Patch Tuesday

Summary: Microsoft has issued a new version of a patch after an earlier version caused some users' machines to suffer the blue screen of death.

Nick Heath

By |

Microsoft has reissued a patch for Windows after an earlier version led to some machines crashing and suffering the 'blue screen of death'.

The first patch, security update 2823324, which fixed flaws in the NTFS kernel-mode driver of Windows, was pulled earlier this month after some users reported getting a "STOP: c000021a {Fatal System Error}" error message after installation.

Read this

Patch Tuesday: Microsoft to fix four critical flaws, all versions of IE at risk again

Patch Tuesday: Microsoft to fix four critical flaws, all versions of IE at risk again

A new version of the patch was made available by Microsoft yesterday.

Windows users with automatic updating enabled will receive the new patch, while those with it disabled will need to install the fix manually.

Microsoft recommends that customers uninstall the earlier security update 2823324 that triggered the initial error message. Instructions for how to uninstall the update and recover affected machines are available here.

The patch fixes three privately disclosed and one publicly disclosed flaw in an NTFS kernel-mode driver that could allow a user to elevate their privilege level. An attacker would need valid logon credentials and be able to log on locally to "exploit the most severe vulnerabilities", according to Microsoft.

The flaws affect versions of Windows XP, Vista, 7, 8 and RT, as well as versions of Windows Server 2003, 2008 and 2012. A full list of the affected versions is available here.

The security update addresses the vulnerabilities by correcting the way that the Windows kernel-mode driver handles objects in memory.

Topics: Security, Microsoft

About

Nick Heath is chief reporter for TechRepublic UK. He writes about the technology that IT-decision makers need to know about, and the latest happenings in the European tech scene.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

35 comments
Log in or register to join the discussion

  • It took them a week to fix this thing?

    It should have been corrected in the first 24hours. In the meantime machines are crashing left and right.

    FAIL
    CaviarBlue
    Reply 3 Votes

    • Uh, no.

      " In the meantime machines are crashing left and right."

      The problem appears to be isolated to a particular piece of software which has been reported to modify the Windows kernel.
      ye
      Reply 5 Votes

      • If, and I say if

        this is true, then it sounds like it's not really Microsoft's fault anyway. At least they fixed it in a relatively quick manner though.
        Sam Wagner
        Reply 3 Votes

        • That's a pretty big IF

          About as wide as the Black Hole of the Universe.
          CaviarBlue
          Reply 3 Votes

        • Not Microsoft's fault

          So, not only Windows does not always run a kernel. But also some third party is writing the NTFS code. (which is by the way, probably true)

          Then the only thing Microsoft are faulty of remains that they actually approved and distributed this patch.

          Unless, you remember that last year there was a security breach at Microsoft, involving the Windows Update infrastructure, which might still be open and some third party is pushing malicious and not well enough tested code (so it crashes) via Windows Update.

          Microsoft are of course innocent.
          danbi
          Reply 1 Vote

      • isolated

        So, it modifies the Windows kernel and then computers crash? You suggest that some computers run Windows without running the kernel? This easily explains why these won't crash.
        danbi
        Reply 1 Vote

        • You fail to understand.

          From what I have learned about this only computers with Kaparsky AV are crashing on this. The kernal is updated and those with Kaparsky fail. This would indicate that the failing is the way kaparsky handles the kernal changes and not MS. However, without full disclosure on all the details of the problem and the machines it happened on it will be difficult for us to know for sure who's fault it was.
          JimITGuy
          Reply Vote

    • Please Please Please Please Please Please Please

      fail in life. I hope you do. Since you have nothing better to do than complain about something that was fixed.

      OR

      Maybe your so perfect that you do not make mistakes, in that case YOU should be writing the patches. So get to work.
      bin00010111
      Reply 1 Vote

      • But I am perfect

        And Linux is GOD so don't you forget it.
        CaviarBlue
        Reply 1 Vote

  • Uh, yes

    If it wasn't that big a deal, they would have let it go for a few months which is their typical modus operandi.
    CaviarBlue
    Reply 2 Votes

    • Uh, no.

      Unless you've got some data to support your claim. Do you?
      ye
      Reply 6 Votes

      • It's common knowledge, @ye

        Just like the Start button or the power cord. Or do I need to research that for you too?

        ;D
        CaviarBlue
        Reply 3 Votes

        • No, it is not common knowledge.

          Merely stating as much doesn't make it so.
          ye
          Reply 5 Votes

          • Yes, it is common knowledge, ye

            You're just play acting dumb again.
            CaviarBlue
            Reply 3 Votes

          • @CaviarBlue

            it is obvious you are NOT just play acting
            john-whorfin
            Reply 2 Votes

          • @ john-whorfin

            Do you always go 'whorfin' all the time?

            lol...
            CaviarBlue
            Reply 1 Vote

        • Uh Huh

          Repeated assertions that something is 'common knowledge' without actually being able to cite a specific example, which are supposedly legion, is a very weak argument, to put it mildly....
          Doctor Demento
          Reply 2 Votes

          • and yet

            Sticking your head in the sand is pretty weak defence strategy either.
            danbi
            Reply Vote

          • Touche, danbi

            Touche
            CaviarBlue
            Reply 1 Vote

          • True....

            ... but apparently there is nothing wrong with this as the Microsoft fanatics do it all the time!
            rahbm
            Reply Vote
CNET Join | Log In | Privacy | Cookies Close