Slashdot Mirror


MS06-049 Causing Silent Data Corruption

Uncle Mike writes "It looks like there is a problem with the recently released MS06-049 / KB920958 patch. If you have compression activated on any folder, then the compressed data is at risk from corruption. New files that are close to a multiple of 4K in size will have their last 4,000 bytes or so overwritten with 0xDF. Although this problem has been reported to Microsoft, as yet there appears to have been no official announcement. "

13 of 205 comments (clear)

  1. interesting by Intangion · · Score: 5, Insightful

    its interesting how when they make a patch that corrupts your data you dont hear anything from them.. but when someone makes a program to allow fair use by opening DRM on their movies they come up with a CRITICAL patch within ours to prevent it. i think that speaks to their priorities, protecting their drm IMPORTANT protecting your data hmm.. not so important

  2. A Paradox... by __aaclcg7560 · · Score: 4, Funny

    If data is being silently corrupted, is there a problem if no one can hear it? That could explain Microsoft's silence.

  3. How to avoid by neonprimetime · · Score: 4, Informative

    assuming you're using Windows

    It has been confirmed that either turning off the compression attribute (disk space permitting) OR uninstalling KB920958 will prevent further loss of data.

    1. Re:How to avoid by PFI_Optix · · Score: 5, Funny

      "assuming you're using Windows " ...if you're using Linux, the process is far more complex. Got a Mac? You're screwed.

      --
      120 characters for a sig? That's bloody useless.
    2. Re:How to avoid by CosmeticLobotamy · · Score: 4, Funny
      I wish I had one of those cute ASCII graphics of a circle going over a tiny guy's head handy. I'll try to make my own, but I'm probably gonna screw this up.


      0
      ----
      | <-You
      /\

      o <-Joke


      ... Crap.
  4. what i think by robpoe · · Score: 4, Funny

    Well, it's interesting that 0xDF0xDF0xDF0xDF0xDF0xDF0xDF0xDF0xDF0xDF0xDF0xDF0x DF0xDF0xDF0xDF0xDF0xDF0xDF

    --
    = Grow a brain...
  5. Re:How does something like this happen by avalys · · Score: 5, Insightful

    If you really have been programming for a long time, you must only be writing very simple programs if you've never had something like this happen, and you think that being "extra careful" is all you need to do to avoid it. What type of programmer does this? Every type of programmer - it's unavoidable.

    The programmer is not to blame here. The real question you should be asking is "What type of QA department fails to catch a bug like this?"

    --
    This space intentionally left blank.
  6. Re:How does something like this happen by CosmeticLobotamy · · Score: 4, Funny

    What type of programmer puts such possibilities or leaks in a program?

    Every programmer that's ever worked on something longer than 6 or 7 lines of code? Except you, of course. I've been in the bathroom after you and am always impressed by the way it smells just like roses.

  7. More background please... by Chris+Pimlott · · Score: 5, Informative

    The summary blurb is rather cryptic. MS06-049 is a patch to... what? Just Windows 2000 or XP too? And this was a patch for some vulnerability, assumedly? Which?

    After a bit of research, here's what should have been included: MS06-049 was an elevation of privledge issue discovered in the kernel of Windows 2000 SP4 only. The patch for the issue, KB920958, appears to have a bug resulting in corruption of compressed folder.

    The title is misleading as well. MS06-649 is the issue and KB920958 is the patch; the patch is what's causing the corruption, not the original issue.

  8. When you have a monopoly by Colin+Smith · · Score: 4, Insightful

    What're your customers going to do?

    --
    Deleted
    1. Re:When you have a monopoly by Tackhead · · Score: 5, Insightful
      > When you have a monopoly
      >
      > What're your customers going to do?

      The guy at the keyboard of a Windows Vista box, using Microsoft Office at work, and Windows Media Player at home is not the customer, he is the product. The customers are Dell, AOL, media licensing conglomerates, and so on.

  9. Re:You can stop now by 0xABADC0DA · · Score: 4, Funny
    I hate to burst your bubble, but you did not check the return code from printf. What if stdout is closed, as in "./a.out >&-"?

    Original troll never writes any bugs, so his hello world is more like this:
    int main(int czArgCount, LPSZ *lpszArgv[]) {
        if (-1 == printf("Hello world!\n")) {
            if (errno == EBADF) {
                if (-1 == fprintf(stderr, "Error stdout closed!\n")) {
                    int fdTty = open("/dev/tty", O_WRONLY, 0666);
                    if (fdTty != -1)
                        write(fdTty, "Hey dumbass dont close my streams\n", 34);
                }
            }
            exit(1);
        }
        exit(0);
    }
  10. Re:How does something like this happen by Rob+Kaper · · Score: 4, Funny

    Plus, why would you pad with 0xDF instead of null? (There might be a reason, but I don't know of it.)

    So this is how Microsoft claims support for ODF. Clever.