Slashdot Mirror


Zero Day Exploit Found in Windows Media Player

filenavigator writes "Another zero day flaw has been reported in Windows Media player. It comes only one day after a serious zero day flaw was found in word. The flaw is dangerous because it involves IE and Outlook's ability to automatically launch .asx files. No fix from Microsoft has been announced yet."

177 comments

  1. Finding holes in a MS product.... by TJ_Phazerhacki · · Score: 5, Insightful

    Seems to be a bit like finding holes in swiss chese... inevitable....

    --
    Physics is nothing like religion. If it was, we'd have an easier time trying to raise money!
    1. Re:Finding holes in a MS product.... by Anonymous Coward · · Score: 0

      15 days old. Way to be on top of things.

    2. Re:Finding holes in a MS product.... by telchine · · Score: 5, Funny

      Is anyone else getting a feeling of Deja Vu?

    3. Re:Finding holes in a MS product.... by jpetts · · Score: 4, Funny

      Who said that?

      --
      Call me old fashioned, but I like a dump to be as memorable as it is devastating - Bender
    4. Re:Finding holes in a MS product.... by blankoboy · · Score: 1

      Or like looking at the opening door of any limousine in Hollywood. Like a car accident, you just cannot look away (oh the humanity!)
      Also, disgustingly inevitable......

    5. Re:Finding holes in a MS product.... by benplaut · · Score: 1

      Anyone else getting a feeling of Deja Vu?

    6. Re:Finding holes in a MS product.... by muszek · · Score: 3, Funny

      Everyone check out this funny movie [free-porn-toolbar.com]

    7. Re:Finding holes in a MS product.... by Anonymous Coward · · Score: 0

      Or a Portsmouth Whore?

    8. Re:Finding holes in a MS product.... by VitaminB52 · · Score: 5, Funny
      Seems to be a bit like finding holes in swiss chese... inevitable....

      Please stop insulting the Swiss. Swiss cheese is completely unlike MS security:

      • Swiss cheese is cheese with holes in it, not holes with cheese around it.
      • Swiss cheese is a quality product.

      If you insists on comparing MS security with a cheese product, then compare it with foam-cheese :-)

    9. Re:Finding holes in a MS product.... by Anonymous Coward · · Score: 0
      Seems to be a bit like finding holes in swiss chese...
      What, you mean hard?
    10. Re:Finding holes in a MS product.... by c4ffeine · · Score: 1

      That's odd. You didn't actually link anywhere, but my default Windows install somehow managed to get hosed anyways.

      --
      "73% of quotes on the Internet are made up" -Ben Franklin
    11. Re:Finding holes in a MS product.... by Anonymous Coward · · Score: 0

      No, I mean full of holes, colonel.

    12. Re:Finding holes in a MS product.... by Anonymous Coward · · Score: 0

      Well that depends on how you cut the cheese.
      The invulnerable people are the ones that get themselves into trouble thinking they are "invulnerable" but nothing truly is. It is our intelligence that minimizes the impact of problems we face.

  2. Another 0-day? by gregleimbeck · · Score: 5, Funny

    Must be Thursday.

    --

    P.S.,

    This is what part of the alphabet would look like if Q and R were eliminated.

    1. Re:Another 0-day? by TheShadowHawk · · Score: 2, Funny

      I thought it was Tuesdays, Thursdays and Sundays when holes are found. I guess they are right on track. :P

      --
      Friends don't let Friends use Internet Explorer.
    2. Re:Another 0-day? by Purity+Of+Essence · · Score: 1

      Microsoft could never get the hang of Thursdays.

      --
      +0 Meh
    3. Re:Another 0-day? by h2g2bob · · Score: 3, Insightful

      Speaking of 0-day, what does 0-day mean, and why is it placed randomly in front of exciting new exploits?

    4. Re:Another 0-day? by neuro_guy · · Score: 1

      http://en.wikipedia.org/wiki/Zero-Day_Attack oh... I must be new here...

    5. Re:Another 0-day? by jfedor · · Score: 3, Informative

      It doesn't mean anything (well, except for "unpatched as of yet" or "disclosed in a not-very-responsible way"). In the pirated movies/games community "zero-day" means that the illegal release was done on the same day that the movie was released to theaters or the game was put on shelves in stores. In the security vulnerabilities community the term is used because many people think it sounds like something a hacker would say (a hacker like Angelina Jolie that is).

      -jfedor

    6. Re:Another 0-day? by DavidTC · · Score: 1

      A 0-day exploit is one that appears before a patch or even an announcement of the security flaw.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    7. Re:Another 0-day? by gstoddart · · Score: 1
      Speaking of 0-day, what does 0-day mean, and why is it placed randomly in front of exciting new exploits?

      In the case of viruses, it means by the time they know there is a potential exploit, it's out in the wild being a real exploit.

      Contrast this with the kind of exploits which someone say "this is a proof of concept vulnerability", but it's not really a dangerous thing since it only shows how someone could potentially use the exploit.

      Basically, it's real, dangerous, and already happening by the time they know anything about it.

      Cheers
      --
      Lost at C:>. Found at C.
    8. Re:Another 0-day? by Anonymous Coward · · Score: 0

      "Speaking of 0-day, what does 0-day mean"

      It's what ISO call Sunday

  3. How is this dangerous? by JanusFury · · Score: 4, Interesting

    I know overflows are bad, but I honestly don't know much about how the allocator in a typical OS or RTL works. Could such a small (2-4 byte) overflow be used to execute arbitrary code? Is it actually possible to use that small of an overflow to screw up the allocator so badly that it'll execute arbitrary code? Or is this just a potential denial of service?

    --
    using namespace slashdot;
    troll::post();
    1. Re:How is this dangerous? by Anonymous Coward · · Score: 1, Insightful

      It depends on what 2-4 bytes can be overwritten with this, obviously. It could be anywhere from completely harmless to critically bad, depending.

    2. Re:How is this dangerous? by LO0G · · Score: 5, Informative

      It depends on your heap allocator. IIRC, on the Windows XP heap (without service packs) an application could be owned with just a 1 byte heap overflow (if the phase of the moon was right). On XP SP2's heap it's WAY harder to exploit overflows, because the heap was hardened against this kind of attack. On Vista, it's even harder, the heap was hardened well beyond what was done in XP SP2.

      I have no idea of how exploitable the various *nix or OSX heap implementations are - I'm sure that some are even more exploitable than XP's heap was (the original 4.2 BSD heap was very exploitable, IIRC), and I'm also sure that some of them are hardened as well as Vista's.

      But heap hardening just makes exploitation harder (this is true of ALL defense-in-depth techniques). Even if your platform has a hardened heap and NX protection and stack canaries and ASLR, it's still possible to successfully exploit a vulnerability - it's many many orders of magnitude harder than if those features weren't present, but it's still possible to attack the system.

    3. Re:How is this dangerous? by Anonymous Coward · · Score: 0

      Incorrect. If the OS is decent, rings of protection surround the kernel. MS makes quick and dirty shortcuts, to get better performance, bypassing security in the process. Guess what?
      If someone discovers these quick and dirty hooks, or able to jag a jump on error vector, you are gone.
      With NX protection it should be impossible, but as this is not the case, then it appears wicked shortcuts /backdoors have been left open. Even if explorer was compromised, do you really want it logging keystrokes. Note, MS never explains WHY Clark Kent applications suddenly get Superman powers. If you look how PING works, you can see how such issues arise.

    4. Re:How is this dangerous? by Anonymous Coward · · Score: 4, Insightful

      MS makes quick and dirty shortcuts, to get better performance, bypassing security in the process.

      Um, what quick and dirty shortcuts? MS uses the same protection model every other x86 OS I know of uses. Kernel runs in CPL 0, user processes in CPL 3. Drivers run mostly in CPL 0. In fact, with MS starting to try to push drivers to CPL 3, they're starting to get better than Linux AFAIK. (I think there are some userspace drivers for Linux, but very few. MS is trying to make that the standard for most types drivers I think.)

      MS's bugs come from a combination of a few things. One is what seems to be a prevalence of buffer overruns. Second is running in administrator mode by default (note that this is an entirely different animal than what privilege level code executes in), and what seem to be an abnormally large number of other misc design errors.

      But the memory model is solid.

      With NX protection it should be impossible

      If you think NX protection makes buffer overrun attacks impossible.. you're living in a dream world. I categorize the types of buffer overrun attacks I know into three types, and NX only solves one of them.

    5. Re:How is this dangerous? by Anonymous Coward · · Score: 0

      How do you stack canaries?They can't burrow.

    6. Re:How is this dangerous? by Anonymous Coward · · Score: 0

      Why would anyone want to spend time on the exploit when there are ready idiots who will click on executable attachments in emails?

  4. This must be by Anonymous Coward · · Score: 0

    the second Zero Day Expoilt, or have i lost count

    1. Re:This must be by mctk · · Score: 4, Funny

      Actually, this isn't the second Zero Day Exploit. The first one was a Nullity Day Exploit. But we don't have to worry about that one.

      --
      Paul Grosfield - the quicker picker upper.
    2. Re:This must be by nwmann · · Score: 0, Redundant

      haha

    3. Re:This must be by CyborgWarrior · · Score: 5, Funny

      And that's how black holes came about. Read your bibles people!! I quote from it:

      "And God saith, I shall divide by zero.

      And big black things did appear.

      And God saith, I shall not do that again."

      --
      If you can't say something nice, make sure you have something heavy to throw.
    4. Re:This must be by Anonymous Coward · · Score: 0

      Dude that Chuck Norris!

      HAHAHAHAHA

      Chuck Norris.... HAHAHHAHAHA

  5. Does Not Affect WMP 11 or Vista by ThinkFr33ly · · Score: 4, Informative

    FYI, this does not seem to affect Windows Media Player 11, which is available via Windows Update or the WMP site.

    It also does not affect Vista, both because Vista comes with WMP 11, and thanks to IE7 running in protected mode. This would likely cause the browser to crash, however.

    1. Re:Does Not Affect WMP 11 or Vista by mpe · · Score: 1

      FYI, this does not seem to affect Windows Media Player 11, which is available via Windows Update or the WMP site.

      Problem is that WMP 11 contains even more DRM. DRM adds much more complexity to a media player, including the trusting of external sites.

  6. It's not an exploit ... by jfclavette · · Score: 4, Insightful

    ..., it's a flaw. I'll be impressed if someone can do anything with a 4 bytes heap overflow that happens at a single spot in the program they don'T control. Under ideal circumstances, they'll be able to tamper an integer in WMP.

  7. Danger: Four-byte programs could be launched? by LostCluster · · Score: 0

    A buffer overflow is a buffer overflow, but if you RTFA... you discover that the maximum overflow of the buffer is four bytes. Anybody know of any four-byte long spyware programs?

    Didn't think so.

    Nothing to see here. Move Along.

    1. Re:Danger: Four-byte programs could be launched? by EvanED · · Score: 3, Interesting

      Um, depending on what's in the data you overflow into, there's still *potentially* plenty you can do. (They're all very unlikely, but the potential is there.) There's other security-sensitive data besides the return address, and other buffer overflow exploits than overwriting that to jump into malicious code.

    2. Re:Danger: Four-byte programs could be launched? by russ1337 · · Score: 3, Funny

      >>>>Anybody know of any four-byte long spyware programs?

      No, but "del /F /S /Q " might fit if you squeeze it.

    3. Re:Danger: Four-byte programs could be launched? by sholden · · Score: 1

      Because there's no such thing as a jump instruction.

    4. Re:Danger: Four-byte programs could be launched? by dextromulous · · Score: 1

      F0 0F C7 C8

      Oh... you wanted a recent one...

      --
      There are two types of people in the world: those who divide people into two types and those who don't.
    5. Re:Danger: Four-byte programs could be launched? by dextromulous · · Score: 1

      Whoops, and by 'recent one' I mean to say 'spyware loading app.' Still, 4 bytes has done damage in the past, and will most likely do so in the future.

      --
      There are two types of people in the world: those who divide people into two types and those who don't.
    6. Re:Danger: Four-byte programs could be launched? by Frankie70 · · Score: 2, Informative


      A buffer overflow is a buffer overflow, but if you RTFA... you discover that the maximum overflow of the buffer is four bytes. Anybody know of any four-byte long spyware programs?


      Are you a moron?
      The code which is executed need not fit into the 4 bytes.

    7. Re:Danger: Four-byte programs could be launched? by Rix · · Score: 1

      This is a pretty stupid comment, but that someone upmodded it is even more amusing.

    8. Re:Danger: Four-byte programs could be launched? by AArmadillo · · Score: 1

      How are you going to execute it? I'm fairly certain WMP does not execute code on the heap at all, much less a try and execute a character string.

      And then, where are you going to jump to? You're in WMP's address space, what in WMP's address space will give you any sort of control over the system? Maybe you could jump to a function that deletes a song from their playlist?

    9. Re:Danger: Four-byte programs could be launched? by camperdave · · Score: 1

      Well, Seeing as you're stuffing a buffer to get an overflow, you might as well stuff it with an exploit program.

      --
      When our name is on the back of your car, we're behind you all the way!
    10. Re:Danger: Four-byte programs could be launched? by empaler · · Score: 1

      The server is now slashdotted (or otherwise FUBAR). Use a mirroring service when posting to Slashdot, nyud.net or archive.org (linked to above article). TY. Interesting article, though.

    11. Re:Danger: Four-byte programs could be launched? by that+this+is+not+und · · Score: 1

      No kidding. I have an 86 byte program running right now in the lab at work.

      It gets sometimes to seem like a bunch of non-nerds have wandered onto this site.

    12. Re:Danger: Four-byte programs could be launched? by DavidTC · · Score: 1

      It gets sometimes to seem like a bunch of non-nerds have wandered onto this site.

      No shit. Someone said 'Hey, the hole is only four bytes' and suddenly we have a bunch of parrots.

      For future references: Many buffer overflows are small. Hence, you don't put the code in the buffer. You put it somewhere else, and jump to it.

      Some absolute goober has managed to notice that 'displacement' requires four bytes, and the JMP one byte, but JMP can also, instead of that, use a single byte that locates the start of the displacement bytes. So all you have to do is find, within 256 bytes, bytes that you can change into being the correct jump location. As this is a data segment, that's rather trivial to find..

      If people on this site don't think hackers can get four bytes of a certain value in a data segment within 256 bytes of this buffer overflow, they're idiots.

      Read here.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  8. If it's not dangerous... by bunbuntheminilop · · Score: 3, Insightful

    as people have commented, then why is it zero day? Doesn't zero day mean there is an exploit already?

  9. zero-day exploit by EvanED · · Score: 2, Insightful

    Since when did a "potentially exploitable heap buffer overflow" become a zero-day exploit?

    1. Re:zero-day exploit by Bargearse · · Score: 2, Informative

      When Slashdot get their hands on it :)
      Neither the linked article, or the eEye alert, say that there is an exploit available, just that it's a flaw.

      And eEye somehow missed listing "upgrade to the unaffected WMP11" as a form of mitigation.

      --
      "Don't break my arse, my bargey wargey arse, I don't think my pants would understand..."
    2. Re:zero-day exploit by Anonymous Coward · · Score: 0
      Since when did a "potentially exploitable heap buffer overflow" become a zero-day exploit?

      That's what happens when a mindless Linux fanboy who doesn't understand the fundamentals of software sees "flaw" and "Windows" in the same article. Conversely, if this were an article posted about any one of the plethora of flaws in various Linux offerings, that same fanboy would cry "troll."
  10. 4 bytes IS ENOUGH by Anonymous Coward · · Score: 1, Insightful

    for those people that don't understand security or how to exploit a buffer overflow, In many cases 1 byte can be enough, you rewrite a function return address with your own address. That does not mean this is definitely exploitable, but don't let the fact that it is only 4 bytes fool you.

    1. Re:4 bytes IS ENOUGH by EvanED · · Score: 5, Interesting

      It's a heap buffer (assuming TFA is right), which means the return address will be nowhere near it. There *could* still be neighboring security-sensitive code, but it's extremely unlikely. Worst case that's remotely likely would be that you corrupt the header that markes the beginning of the next heap block and wreak havoc with future malloc calls. Probably nothing controllable though. This *really* isn't that big of a deal, and calling it a zero-day exploit is downright libel.

    2. Re:4 bytes IS ENOUGH by bluefoxlucid · · Score: 4, Interesting

      Worst case that's remotely likely would be that you corrupt the header that markes the beginning of the next heap block and wreak havoc with future malloc calls. Probably nothing controllable though.

      Alter the next heap header to point to a location on the stack as the next free block, and send another chunk of data so malloc() is called and allocates from there. Then write your code/retp change and wait. (Or something equally bizarre)

      A couple bytes overflow in the heap is abusable enough to screw with pointers; and in some cases it suddenly turns into a big overflow in situations we didn't predict (this happened with an old libpng CVE, and with an Apache flaw where the overflow was always exactly "k`" until someone figured out how to do better).

    3. Re:4 bytes IS ENOUGH by EvanED · · Score: 1

      I'm not saying that something like this isn't exploitable, I'm just saying that the chance is extremely low.

      For your plan to work:
      1. The following memory would likely have to be deallocated (this depends on the malloc implementation, but assuming that it keeps track of a free list, the block that you corrupt would have to be deallocated before that address was used for anything), so the following would have to be done at the first allocation following this deallocation
      2. You would have to be able to determine a valid stack address to make it point to
      3. The buffer it allocates would have to be for unchecked/mischecked user input and not just internal storage that you don't have control over
      4. You would have to know when you were able to write to it

      Stranger things have happened in security, that's for sure, but the chances there are pretty out there.

      (Furthermore, the MSVC malloc block header would have to be amenable to this attack, which it might not be.)

    4. Re:4 bytes IS ENOUGH by Anonymous Coward · · Score: 0

      As an Introduction to exploiting heap overflow, I'd recommend the following papers:
      An article from heise security and a tutorial by w00w00.

    5. Re:4 bytes IS ENOUGH by Anonymous Coward · · Score: 0

      calling it a zero-day exploit is downright libel

      You seem to not know what either "zero-day exploit" or "libel" mean.

      Libel I'll leave to your dictionary (you do own one, don't you?), but you'll probably have to be told that a "zero-day exploit" has nothing to do with severity -- it means that working exploit code was released on the same day as the vulnerability was announced.

    6. Re:4 bytes IS ENOUGH by EvanED · · Score: 1

      you'll probably have to be told that a "zero-day exploit" has nothing to do with severity -- it means that working exploit code was released on the same day as the vulnerability was announced.

      Um, where's the working exploit code?

      TFA only says it's "potentially exploitable".

  11. Maybe they should Pay One hexadecimal dollar? by Elvis77 · · Score: 0, Offtopic

    It worked for Knuth

    --

    The man in black fled across the desert, and the gunslinger followed (SK)
  12. Hmm... by Anonymous Coward · · Score: 4, Funny
    1. Re:Hmm... by MichaelSmith · · Score: 1

      It would be funnier if technocrat carried that advert.

  13. All it takes is a jump instruction. by Anonymous Coward · · Score: 5, Informative

    x86 processors have a local jump instruction that is 4 bytes long. If the exploiter is able to get his code loaded within range of that jump instruction, you're fucked. And really, getting code loaded like that is not a difficult thing to do.

    In fact, many x86 operating systems have used such a technique to dynamically patch kernel code. They insert a couple of nop operations after a function prologue. These operations normally do nothing, but can be replaced with a jump instruction at runtime. This allows for the instructions of the existing function to be replaced with ease.

    1. Re:All it takes is a jump instruction. by EvanED · · Score: 4, Interesting

      This is a heap buffer, assuming TFA's right. What programs execute instructions from the heap and so have the potential to be overwritten by a jump?

      At absolute worst, you could do what at least one paper calls a non-control-data attack and corrupt some other piece of data that was next to it in the heap. Except every malloc implementation I know puts a header struct at the beginning of each block, so even if two pieces of heap data ended next to each other you wouldn't be able to reach the actual data with just a 4 byte overflow, and the best you could hope for is to corrupt the header. This is very unlikely to have any exploitable effects, and is just likely to kill the process.

    2. Re:All it takes is a jump instruction. by QuantumG · · Score: 1

      x86 processors have a local jump instruction that is 4 bytes long. Wow, news to me. Is this just a regular 2 byte branch instruction with two prefixes on it? Or maybe you're thinking of a 5 byte jump instruction.
      --
      How we know is more important than what we know.
    3. Re:All it takes is a jump instruction. by tjcrowder · · Score: 2, Interesting
      And really, getting code loaded like that is not a difficult thing to do.

      It's easy (in the context of attacking a computer via a media file) to load code into a data segment, sure. But not into a text (code) segment. So the jump instruction does a local jump to -- oops, access violation.

      It is truly amazing, though, that six-seven years after Microsoft really started talking big about dealing with their security problems, they still haven't managed to complete a code review to deal with buffer overrun vulnerabilities. I'm sympathetic to their massive codebase, but in many cases finding buffer overrun vulnerabilities is trained monkey work -- and Microsoft has the money to contract a large number of monkeys, train them, and sic 'em on the code. Sure, there's also a lot of work there for skilled programmers and even engineers -- a lot of their stuff is written in languages like C and C++ where you can pass a buffer to a method without its bounding information -- but surely they could have the monkeys at least flag up what the more skilled people need to look at. It's been a long time, guys. Lots of code, sure, but lots of years, too.

    4. Re:All it takes is a jump instruction. by runderwo · · Score: 1
      x86 processors have a local jump instruction that is 4 bytes long.

      x86's local jump is two bytes long. One byte for the prefix (74/75 for conditional, EB for unconditional) and one byte for the offset.
    5. Re:All it takes is a jump instruction. by plover · · Score: 1

      a lot of their stuff is written in languages like C and C++ where you can pass a buffer to a method without its bounding information

      And it took them until Visual Studio 2005 for them to bite that last bullet. In case you haven't used it yet, they've added a set of "safer" routines to the standard C runtime library. They They are not backward compatible. Now, instead of sprintf(), you call sprintf_s(), which takes the traditional output buffer pointer plus a new parameter indicating the length of the output buffer. It also validates the format string, although if you let the users modify that you'll still have problems (and the documentation now specifically warns the developer that this is a security issue.) And they've added a new set of warnings to the compiler to let you know if you're still using the deprecated old routines. You can turn them off, of course, but Microsoft recommends you fix your code instead.

      This was really a huge step. With it, they are forcing programmers to at least consider what happens when they use pointers. Sure, a programmer can work around these new routines, they can code sloppily, they can hard code incorrect values for buffer lengths, they can ignore error codes. Nothing will ever prevent a C programmer from being able to shoot him or herself in the foot. But now there's a better toolset that can help people identify these problems before the code is released.

      --
      John
    6. Re:All it takes is a jump instruction. by ultranova · · Score: 1

      At absolute worst, you could do what at least one paper calls a non-control-data attack and corrupt some other piece of data that was next to it in the heap. Except every malloc implementation I know puts a header struct at the beginning of each block, so even if two pieces of heap data ended next to each other you wouldn't be able to reach the actual data with just a 4 byte overflow, and the best you could hope for is to corrupt the header. This is very unlikely to have any exploitable effects, and is just likely to kill the process.

      Can you corrupt the blobl length indicator ? Because if you can, you can make the next memory blob larger than it was before it was when it was allocated, so that when free is called on it, the resulting free memory area (as seen by malloc) actually overlaps the next blob. Then when something gets put there, it (may) overwrite parts of the next blob, and if it had things like function pointers, they are now replaced with new values - possibly read from the file itself.

      Now, obviously I'm assuming quite a lot about how malloc, free and WMP work, and even if I was correct, this is not an easy exploit to do... But it's not impossible either.

      As a side note I have to admit I kinda like all these new exploits coming out. With DRM in Vista it's comforting to know that the chains and locks are being made by the village idiot.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    7. Re:All it takes is a jump instruction. by Anonymous Coward · · Score: 0

      > x86 processors have a local jump instruction that is 4 bytes long. If the exploiter is able to get his code loaded within range of that jump instruction, you're fucked. And really, getting code loaded like that is not a difficult thing to do.

      This is nonsense. x86 jump instructions come in two, five, and six-byte flavors, but that's all irrelevant for a heap overflow, or in fact for any type of buffer overflow whatsoever.

  14. GG Misleading Post by PixieDust · · Score: 5, Insightful
    Ok, so this flaw is there. It's a bug.

    Doesn't affect my Vista machine. Nor my XP Pro machine running IE7 + WMP 11.

    Seeing things like this, I can't help but wonder what it might look like if every time a flaw was discovered in *Nix, and a security advisory (even if barely remotely applicable, as in this case) were released,and slashdotted. Maybe this post is flamebait too (seems to be my trend as of late), maybe not. But the title of this particular post, is pretty misleading.

    0 day flaw! Congratulations. It's software. I still play games that if they run for more than 2 hours I'm lucky. The real problem is the testing, and the coding that goes into these. You fix one thing, and something else inevitably breaks.

    How often does a kernel update in Linux break something that you now have to update, or sometimes roll back alltogether because they won't work.

    This post is as Overdramatic as going nuts every single time something in Linux broke or didn't work right. Sometimes MS deserves to be thumped on the head. This time though, seriously, come on. Tell you what, run your 4 byte program that is gonna hax0r my computer. I invite it, might give me something to do.

    1. Re:GG Misleading Post by lahvak · · Score: 1

      4 bytes are more than enough. All you need to do is load your program into that buffer, and put a jump instruction to the entry point of the program (if you are overwriting executable code) or simply the address of the entry point (if you manage to overwrite a function return address). It seems that in this case, the memory being on the heap, it's none of those two cases, on the other hand, from my pld days of programming in assembly under DOS, we did all sorts of tricks with allocating memory, loading instructions into it, and executing them. Sometimes this was the only way to overcome various limitation of the architecture (combination of 8086 and DOS).

      --
      AccountKiller
    2. Re:GG Misleading Post by Spiked_Three · · Score: 1

      Not a broken Linux, but a broken Apple;

      http://news.com.com/MySpace+to+Apple+Fix+that+worm /2100-7349_3-6141031.html

      Reported to slashdot 3 days ago, story accepted, never published.

      You are soo correct, if it is Microsoft it is critical news. If it is anyone else, it's covered up.

      --
      slashdot troll = you make a compelling argument I do not like the implications of.
    3. Re:GG Misleading Post by Anonymous Coward · · Score: 0

      You are soo correct, if it is Microsoft it is critical news. If it is anyone else, it's covered up.

      Meh.

      If it is Microsoft, it affects the majority of the world's (home/office) computer users. If it is anyone else, it doesn't. With market dominance comes great(er) responsibility.

      It's not that hard a concept to grasp, is it?

      To Microsoft (and its fanbois): If the heat is too much for you, do something about the underlying problems, or get the fuck elsewhere. Seriously.

    4. Re:GG Misleading Post by Anonymous Coward · · Score: 0

      So you are suggesting that news about anything other than Microsoft isn't really news.

      Wow, I wonder how many readers of this site agree with you.

    5. Re:GG Misleading Post by jZnat · · Score: 1

      It was probably rejected because nobody at Slashdot cares about MySpace in the slightest.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    6. Re:GG Misleading Post by nakkenakuttaja · · Score: 1

      Why on earth are you using this kind of software set-up???? Looks like you are a serious MS-fanboy!!! Are your comments really something to take seriously or just pure FUD? I believe Slashdot readers are educated enough and know what to think about your comments.

    7. Re:GG Misleading Post by PixieDust · · Score: 1
      Think what you want.

      I tell you what, let's work together here. You create something that will take advantage of this bug (which I maintain is being overdramatized). I will create a test machine that uses IE6 and WMP 10 (or 9 if you prefer). We will then perform a test. Attempt to exploit this bug, and we'll see if it's something dangerous to be concerned about.

      As for whether or not I'm an MS fan-girl. *shrug* Windows works quite well for me, always has. I have nothing in particular against Linux, Unix, or Mac, just that they aren't right for me. I still use Linux from time to time (I get quite bored with Windows), and for a brief time (and this is totally absurd, and a scary thought) I was a Unix SysAdmin. When someone can provide me a valid list of reasons to switch, I will. But until I can get all the same features, compatability, etc. I'm going to stay right where I am as far as home use goes. I can build a Linux machine without much trouble, and troubleshoot most things, and in general know my way around well enough to get by. I'm no power user of Linux by any sense of the word. Though I do have to say, I'm starting to like some of the multimedia applications that I've used a bit, and mplayer has been my preferred media player for well over a year now.

      Hell I generally don't even use WMP for the most part. MS Fan-Girl? Maybe. But I know good software when I see it. Or perhaps, I know software which suits the needs of the majority of users, and for what it is, and what it does, it works well. Would I recommend mplayer to sally joe public? Probably not. It's too bulky. Do I use it? Absolutely, and I love it. Would I recommend Linux to sally joe public? In a word, No.

      And by sally joe public, I mean the person that sits on the phone screaming at me how they can't get into their system, they just installed Linux. It's taking them to their email ~user@machine# and they have a blinking cursor. This happens EVERY TIME the user boots their computer, it asks them for their user name and password, they put it in, then it doesn't do anything for a minute, then their screen just goes black and it drops them to that. It says something about an error, and now they're at their email.

      No, I'm not going to recommend Linux to someone like that (they had actually had a friend tell them they should use Linux, so they did). Could I take care of that? Easily. Can the USER? Nope. Not a chance. And I don't know about anyone else, but I don't particularly want to be 'on-call' 24/7/365 and constantly busy helping a friend with their Linux installation. I don't like doin git for Windows either, but thankfully Windows doesn't require it much.

      As for my software setup. It perfectly performs what I need it to perform. Linux would not. Mac OSX would not. I run no virus or spyware protection, I use the Windows firewall, and I browse using Internet Explorer (nearly) exclusively. I have 0 issues. And have had 0 issues since I began running this way a loooooooong time ago. I'm not a USER. *shrug*

  15. Ever hear of the JUMP instruction? by Anonymous Coward · · Score: 4, Interesting

    Umm, do you know what you're talking about? All you do is jump over to your NOOP slide or whatever embedded in the data that slides all the way down to the program disguised as some part of the ASX file.

    I don't know how large they are in x86 assembly, but the 86HC11 I used to write for didn't have any instructions bigger than four bytes unless I sadly misremember. Four bytes would've been plenty.

    Don't laugh. Plenty of exploits have been coded that have more difficult requirements for the exploit to work.

    1. Re:Ever hear of the JUMP instruction? by Anonymous Coward · · Score: 0

      The shortest control-flow instruction in x86 is 5 bytes. Even if that weren't true, writing a jump instruction at some point in the heap won't help you. You need a FAR more nuanced (and *extraordinarily* unlikely) attack.

  16. Re:You Could... by Neil+Hodges · · Score: 1

    Any piece of software is vulnerable to these sorts of attacks; the only way to prevent them is with flagging memory as unwritable (and possibly randomizing the memory blocks). Thank you, PaX.

  17. Re:Fix found for zero day flaw by Gothmolly · · Score: 1, Funny

    Where's the "-1, Gay" modifier when you need it?

    --
    I want to delete my account but Slashdot doesn't allow it.
  18. Re:You Could... by Anonymous Coward · · Score: 0

    Um, how can you flag memory as unwritable if you need to write to it?

  19. Merry Christmas!!! by malzraa · · Score: 0

    to botnet creators.

  20. No plans to fix the Word flaw by jginspace · · Score: 4, Interesting

    Microsoft have just given advance notification of what their bundle of patches to be released next Tuesday will contain. There are five general Windows bulletins there - no surprise that the most severe is 'critical' - but I'm kind of surprised to see they have no intention of shipping any Office-related fixes.

  21. It could be fixed already by Anonymous Coward · · Score: 4, Funny

    But it is not a flaw in the DRM, ao why ahould Microsoft care?

  22. Re:WMP11 Has Serious Exploit by mpapet · · Score: 1, Insightful

    It's the one where Microsoft decided they will decide when and where and on what devices to allow you to play your media.

    Any bright minds out there that willingly use these things lost control of all of their personal media.
    http://www.microsoft.com/windows/windowsmedia/play er/faq/drm.mspx

    http://www.theinquirer.net/default.aspx?article=34 523 is in plain engrish.

    I certainly hope you aren't running either Vista or WMP11.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  23. Has this been tested? by DavidD_CA · · Score: 1
    From the article:

    Exploitability due to the corruption of the adjacent heap block's header is assumed likely but research is ongoing. It's "likely"?

    That sounds to me like something could *potentially* happen, but they haven't been able to actually prove it yet. And, the date on this discovery (according to the source article) was over two weeks ago. By now, wouldn't they have concluded something with their research?

    The company does, however, sell a product to help mitigate "issues" like this.. which they link to at the bottom of their article.
    --
    -David
    1. Re:Has this been tested? by EvanED · · Score: 1

      That sounds to me like something could *potentially* happen, but they haven't been able to actually prove it yet. And, the date on this discovery (according to the source article) was over two weeks ago. By now, wouldn't they have concluded something with their research?

      No... not at all. They're just very liberal with their definition of "zero-day"...

    2. Re:Has this been tested? by Anonymous Coward · · Score: 0

      They already have PoCs for this bug, they just haven't released it because the IDS/IPS/Security industry as a whole is a good ole boy network and everyone is waiting for all of the vendors to get their products up to date before any PoCs are being released. This bug was discovered by an unrelated researcher out of Russia but was reported as a DoS, eEye came out a few days ago and said no its an RCE-able bug (remote code exec).

    3. Re:Has this been tested? by SkiifGeek · · Score: 1

      It seems that eEye are only linking to the '0-day' (for loose definitions of 0-day) vulnerabilities that their products can detect and protect against. There are many, many more 0-days that are out there, including an .asx 0-day (a true 0-day) which is more serious than this, and older as well. The only difference is that it doesn't target WMP.

      The recent coverage of ASX Playlist issues in various security mailing lists and forums seems somewhat strange. For the uninitiated, here is a quick wrapup:

      XMPlay ASX buffer overflow PoC code posted to milw0rm - 21 November

      This PoC demonstrated an exploitable buffer overflow condition in the handling of 'ref href' URIs. A CVE entry (CVE-2006-6063 - though this only identifies the .m3u method of exploiting the vulnerability) appears around the same time, and reporting is carried by the usual third parties. With no fix present, this remains an effective 0-day (plus, with existing malware targeting .asx files it could make for interesting real-world use).

      Windows Media Player DoS code posted to BugTraq - 22 November

      Oddly, this code represented an almost exact duplicate of the buffer overflow demonstrated the day before, only with the exploit payload removed and replaced with a bunch of 'A's, and fails to draw much interest from third parties. It isn't until eEye publishes data on this issue (and increases the perceived threat posed) on their 0-day reporting / information site that it attracts some attention from other reporting parties (such as FrSIRT on 7 December), though uptake is slow.

      Leaving Chinese Soup's critique (BugTraq) of eEye's analysis aside (why they haven't identified on the XMPlay vulnerability is another question), users need to be aware that if they replace WMP with XMPlay as the default handler of .asx content, then they are potentially creating a much riskier environment than if they accept the current DoS risk against their platform.

      If this particular code release had appropriate accompanying documentation, it would be possible to work out whether it is a derivative of the earlier code, or fortuitous timing on something found independently.

      Criticism has been recently levelled against third party reporting bodies for failing to adequately investigate reports (after one of the recent MoKB OS X corrupted .dmg file handling errors), and the way that information is flowing between, and being distributed by, third party reporting bodies in this case is showing similar patterns.

      In summary:
        - There is a known 0-day targeting a vulnerability in XMPlay's handling of malicious .asx (and other content types) data passed via 'ref href' that can lead to arbitrary code execution.
        - There is a known DoS targeting WMP that is exploited via a long string passed via 'ref href' and using the .asx media type
        - There has been no proven link between the two disclosures
        - It has yet to be shown that the WMP vulnerability leads to arbitrary code execution
        - The advice to replace WMP as the default .asx filetype handler can lead to an increased security risk if the replacement application is XMPlay (accepting arbitrary code execution in an effort to avoid a DoS).

    4. Re:Has this been tested? by GigsVT · · Score: 1

      Avoid the temptation to double post like this. It makes people that read nested very annoyed.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  24. Tomorrow's zero day exploit by postmortem · · Score: 1

    in.... Linux

  25. Anti-Troll Measures by Anonymous Coward · · Score: 2, Funny

    Where's the "-1, Gay" modifier when you need it?

    It got removed from slashcode at the same time the "-1, Nigger" mod went.

  26. Re:Fix found for zero day flaw by The+MAZZTer · · Score: 0, Offtopic

    As a Windows user experimenting with Linux, I managed to make Linux kernel panic the very first time I booted it from my hard drive.

    Of course I was trying to configure grub to triple boot manually... on Slackware. Ubuntu has it's own share of problems, like thinking my computer is running on GMT and "fixing" my clock for me to what it thinks is the actual local time. Then when I set it to the correct time, I can't use sudo or su for five hours because of a stupid sudo timestamp (I eventually figured out how to clear it but Joe Average wouldn't have).

    The one really neat thing Linux has going for it is packages and automatic program installation and such... of course Joe Average isn't going to care about such things, since he just dumps everything in Program Files anyways and never knows.

  27. Re:Fix found for zero day flaw by Anonymous Coward · · Score: 0
    Where's the "-1, Gay" modifier when you need it?

    Here, apparently.
  28. Re:Fix found for zero day flaw by Valacosa · · Score: 1, Informative

    He's not gay. If he were gay, he'd be telling us to buy a Mac.

    --
    "Live as if you'll die tomorrow." Ridiculous. You could die later today.
  29. Re:Fix found for zero day flaw by inode_buddha · · Score: 1

    Goatse obviated the need for it. I suppose we *could* bring it back for the MS exploit articles, though.

    --
    C|N>K
  30. To quote Bizarro Gates by WankersRevenge · · Score: 1, Funny

    4 bytes should be enough for anybody

  31. Re:Fix found for zero day flaw by Anonymous Coward · · Score: 0, Offtopic

    First thing you you should do on a new N00buntu installation is `sudo passwd root` and set a strong password, so you don't have to deal with that sudo bullshit. If anyone gives you shit over this tell them an anonymous coward from slashdot said they are fucking idiot....and then backhand them across the face.

    Good luck in your Linux adventures, and by sure to watch out for the evil binary blob monster.

  32. Re:WMP11 Has Serious Exploit by Propaganda13 · · Score: 2, Funny

    Just re-installed Windows on a computer and updated everything except WMP11.

    Don't worry I installed Debian too.

  33. Re:WMP11 Has Serious Exploit by Anonymous Coward · · Score: 1, Interesting

    With WMP11, both your DRMed music and your clear music will play. On other platforms, only your clear music will play. Well, on the Apple platform your Apple DRMed music will play. (Speaking of Apple, it should be known that their DRM is just as bad).

    If you don't like DRM, don't buy DRMed music. WMP11 will play your clear music just fine. Meanwhile, people who are buying DRMed music will be able to play it in WMP11 without affecting the experience of those who refuse to buy DRMed music.

    Also, it is not Microsoft that chooses when, where, and on what devices you may play your media. They merely provided the mechanisms that allow content providers to make those decisions. Content providers are free to let you do anything you want with your music, or provide clear content entirely. Again, if you think a content provider's policy is too restrictive, do not buy music from them.

    In short, I fail to see where this is a failing of WMP11 or Vista.

  34. The new "thing" by SupplyMission · · Score: 1

    Is it just me, or did these "zero day exploits" suddenly come out of nowhere?

    We used to hear about all kinds of interesting security vulnerabilities, flaws, buffer overruns, etc. Did someone reclassify everything as a "zero day exploit"?

    1. Re:The new "thing" by EvanED · · Score: 1

      Apparently so.

      Theoretically, a zero-day exploit is one that can be executed *right now*, before there's a chance to patch. However, considering that the advisory says it's "potentially exploitable" even though it was published some 16 days ago seems to be stretching the definition of "zero." The blog MS linked to was alarmist, and /. is downright defamatory.

    2. Re:The new "thing" by DavidTC · · Score: 1

      This is not a 0-day exploit by any sane definition, because, duh, there's no fucking 'exploit'.

      It's an unpatched vulnerability. An exploit is a program that can use a vulnerability. An exploit 'in' WMP would mean that it's attacking other computers.

      I don't know who the hell is writing the headlines here, but they're idiots.

      And 'zero-day' is wrong too. 0-Day exploits are ones that exist before a vulnerability is found, or at least before it's well known, or right after (within the same day) it's known about. 0-Day means 'out the same day', although it also applies to 'out in advance'.

      Even if there were an exploit written now, it wouldn't be '0-Day', because everyone has known about the hole for two weeks.

      I know the article said '0-day flaw', not '0-day exploit', and that is even worse as that is completely meaningless, unless it's applying to flaws that are discovered the same day they are created or something.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  35. Re:WMP11 Has Serious Exploit by that+this+is+not+und · · Score: 1

    Any bright minds out there that willingly use these things lost control of all of their personal media.

    You're telling me that I've 'lost control' of the huge collection of Old Radio Program MP3s I have stuck in folder on the D:\ drive???

    It's ludicrous to think that my, or anybody's 'control of all personal media' is governed by a binary on some Windoze box in a corner of their room.

    I suppose it matters if you only have one peecee in your 'room' and mom decrees that you can only have Windoze installed on it.

  36. Zero-day exploit by Schraegstrichpunkt · · Score: 3, Funny

    Was a new version of Windows Media Player released today or something?

  37. How's this a zero-day flaw? by Anonymous Coward · · Score: 0

    Look the definition up.

    If there's no exploit yet, it's not a zero-day flaw, it's just a hole in the software that *can* be exploited, either today or later.

    Zero-day means that *right now* there are people already exploiting it, which the article does NOT state.

  38. It really whips the Llama's ass! by wizzard2k · · Score: 1
    FTA:
    The best way to protect against it right now is to open windows explorer and click on the tools menu, then folder options
    Click on the file types tab, and scroll down to "ASX". Either delete it (Windows will no longer know what to do with ASX files - BE CAREFUL! -, or change to another program.

    For me, winamp has always handled as much of windows media player file types as possble.
  39. still not zero day by ILuvRamen · · Score: 0

    "Zero day" is only used cuz it sounds scary. First of all, it sounds like one particular problem with entering zero as a value for day in a program. Second, they said they definition specifically is an exploit that was just discovered and used immediately "in the wild." How the hell would they know how long people have been exploiting it and how long they've known about it before they implemented it. It's really just a stupid media ploy. Btw I'm a programmer and I can tell you that this exploit is relatively not dangerous at all because it's so difficult to exploit compared to other wide open holes that have been discovered like that one in IE that lets sites read your passwords for other sites without you really having to do anything or knowing it's happening. Now THAT is a security hole. I think a bigger security hole is the fact that wmv files can launch links to webpages and force you to download a file from them and they designed it that way on purpose because of DRM!!!!!

    --
    Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
  40. Re:WMP11 EULA Time Bomb by mpapet · · Score: 2, Interesting

    You're telling me that I've 'lost control' of the huge collection of Old Radio Program MP3s I have stuck in folder on the D:\ drive???

    Uncertain. Hopefully you aren't getting the content from CD's. This is verbatim from the EULA:

    "If the file is a song you ripped from a CD with the Copy protect music option turned on, you might be able to restore your usage rights by playing the file. You will be prompted to connect to a Microsoft Web page that explains how to restore your rights a limited number of times."

    So, the CD you paid for unlimited rights to play where you want has been revoked. Permanently.
    And you agreed to it. Can you go back to WMP10?

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  41. Re:WMP11 EULA Time Bomb by that+this+is+not+und · · Score: 1

    What is this 'copy protection music option' and what bit does it set in my Old Radio Show .mp3 files??

    I paid for unlimited rights to play the CD. So I stick it in a CD player (i.e. in the dashboard of my car) and it plays.

    Dunno what any of this has to do with Windows. I've certainly not 'lost control' of anything.

  42. It is a new Slashdot tag by flyingfsck · · Score: 1

    It is just slightly below: "Nothing to see here, please move along".

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  43. Re:You Could... by stonedcat · · Score: 0

    ....please mod parent down to fucking retard, mod parent's parent down to master of the fucking obvious.

    Have you ever tried installing windows media player past version 7 in wine? Even if you did manage to get it working and intentionally direct your media player to an exploit file, the exploit (if it worked at all) would be restrained to wine's boundaries... so unless you're ignorant enough to mount / as the virtual c drive in wine... there's no way this would even effect your linux box in the least. And this is all specualtion, I doubt you could even get it to do anything but crash wmp and wine.

    --
    You can't take the sky from me.
  44. Re:You Could... by flyingfsck · · Score: 1

    Not true. It only happens if input is not range checked. It usually means that some lazy idiot used one of the zero terminated string functions in C, instead of the new ones that have an explicit length. For example, strcpy() instead of strncpy().

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  45. Slight difference by ZxCv · · Score: 4, Insightful

    This flaw is not "barely remotely applicable".

    The vast majority of Windows users do not run Vista, IE7, or WMP11, even though all are technically available.

    So this particular flaw affects most Windows users, and is thus important to those that have to deal with these users and/or their computers.

    --

    Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
    1. Re:Slight difference by DavidTC · · Score: 1

      The vast majority of Window XP users use IE7 now. It came out in the automatic updates a month ago.

      I don't know about WMP11, or what percentage use XP.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  46. Re:WMP11 Has Serious Exploit by Anonymous Coward · · Score: 0

    Having your computer decide for you what you're allowed to see or hear is something many people do not like.

  47. Zero day exploit??? by advocate_one · · Score: 1

    wtf, where's the exploit??? This is just an announcement of a weakness... TFA calls it a Zero-Day Flaw...

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  48. Stop the Zero Day crap! by paniq · · Score: 1

    Back in the days when I was young, 0-Day was warez-slang, but now it has become some mainstream buzzword.

    Not a long time until they start to replace "new" for "zero day" in advertising. Remember where you heard it first.

    The Zero Day Kids On The Block. Zero Day York, Zero Day York.

    --
    Do not trust this signature.
    1. Re:Stop the Zero Day crap! by Anonymous Coward · · Score: 0

      Unfortunately, "new flaw" implies that there is a patch for the issue. It can also imply that the vendor is aware of the issue.

      0-day implies that there is no patch, and that the vendor may *not* be aware of the issue. It also implies that the exploit is in the "wild" and you could get hit by it without knowing what to do (e.g. mitigation).

      I agree with you that I don't like 0-day "flaw" because it isn't necessarily exploitable, but it does imply that the vendor probably isn't aware of the issue.

      How would you define these terms?

    2. Re:Stop the Zero Day crap! by paniq · · Score: 1

      What about just "flaw"? If it wasn't new and a patch was available for it, it certainly wouldn't be on Slashdot. If Slashdot reports about a flaw, it _has_ to be new and unknown. Otherwise, I'd really wonder why I'm subscribing to the RSS feed ;)

      Most of the time, the articles might just run fine without any "Zero Day" at all.

      --
      Do not trust this signature.
  49. A good chance to try VLC by Giorgio+Maone · · Score: 2, Informative

    VideoLAN - VLC Media Player is an all-in-one open source and cross platform program which does much more than WMP: it's an user-friendly player, but also a powerful and flexible transcoder for almost every audio/video format and even a stream server supporting various network protocols.

    Worth a try as a better replacement, especially for power users.

    --
    There's a browser safer than Firefox, it is Firefox, with NoScript
  50. Just In Time For Vista Marketing by Anonymous Coward · · Score: 2, Insightful

    How surprising is this. MS have been sitting on this information for a long time and now it's the most profitable moment to announce them. "Yes, xp has these problems, just upgrade to vista and they'll go away."

  51. Lovely.. by cheros · · Score: 1

    So, I can't open Word files because of an unfixed risk, and I can't open sound files because of an unfixed risk. Wonderful if you're running the average business..

    After switching to OpenOffice and VideoLAN, I guess the leap to Linux isn't that far if it wasn't for the fact that you'd have to switch a whole infrastructure and find a new support environment. Not that easy, but more and more attractive, and it appears to have an ever improving ROI...

    --
    Insert .sig here. Send no money now. Owner may sue, contents will settle. Batteries not included.
  52. Re:WMP11 EULA Time Bomb by Anonymous Coward · · Score: 0

    "If the file is a song you ripped from a CD with the Copy protect music option turned on, you might be able to restore your usage rights by playing the file. You will be prompted to connect to a Microsoft Web page that explains how to restore your rights a limited number of times."

    Key part bolded. It's optional. Plus it's only available if you choose to rip to WMA, which is also optional. What's with the FUD?

  53. Fix by pe1chl · · Score: 1

    Maybe instead of (or in addition to) fixing things like this, they should distribute a tutorial on how to setup the system to use less-privileged users instead of being logged in as Admin all the time.

    Also, they should more actively spread bad press about companies that release products that require administrator rights to be used.
    Those companies should be pointed out as part of the reason for security problems and hacked systems.

  54. Re:WMP11 Has Serious Exploit by Anonymous Coward · · Score: 0
    Don't worry I installed Debian too.
    Why on earth should I worry?
  55. Re:WMP11 Has Serious Exploit by Crayon+Kid · · Score: 1

    Oh yeah? How about when I rip a CD to HDD and it adds DRM to the files? How about when it doesn't let me watch a cable show (which I bloody payed for already) because it has DRM bits in it that say I can't watch it on my computer? How about not being able to record TV shows for personal use (which is perfectly legal) for the same reason? How about one day a vendor pushes a recall for certain DRM'ed files through a WMP update and I lose the ability to play my own freaking files?

    Yeah, WMP and DRM are really "good" to me.

    --
    i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
  56. Re:WMP11 Has Serious Exploit by Anonymous Coward · · Score: 0

    With WMP11, both your DRMed music and your clear music will play.

    What DRMed music? You don't actually buy that stuff do you? Sucker.

  57. More problems with the programming language C! by master_p · · Score: 1

    Again, please please please let's all stop using C and use an alternative like Ada, Cyclone or D!

    And no, this is no troll, it's reality: with a language like C, problems like buffer overflows are very easy to do...

    At this day an age, a buffer length check is not a serious hit on performance!

    1. Re:More problems with the programming language C! by Anonymous Coward · · Score: 0

      I'll bet you're pro gun control too.

  58. There's More - If you read the security lists by SkiifGeek · · Score: 2, Informative

    The recent coverage of ASX Playlist issues seems somewhat strange. For the uninitiated, here is a quick wrapup:

    XMPlay ASX buffer overflow PoC code posted to milw0rm - 21 November

    This PoC demonstrated an exploitable buffer overflow condition in the handling of 'ref href' URIs. A CVE entry (CVE-2006-6063 - though this only identifies the .m3u method of exploiting the vulnerability) appears around the same time, and reporting is carried by the usual third parties. With no fix present, this remains an effective 0-day (plus, with existing malware targeting .asx files it could make for interesting real-world use).

    Windows Media Player DoS code posted to BugTraq - 22 November

    Oddly, this code represented an almost exact duplicate of the buffer overflow demonstrated the day before, only with the exploit payload removed and replaced with a bunch of 'A's, and fails to draw much interest from third parties. It isn't until eEye publishes data on this issue (and increases the perceived threat posed) on their 0-day reporting / information site that it attracts some attention from other reporting parties (such as FrSIRT on 7 December), though uptake is slow.

    Leaving Chinese Soup's critique (BugTraq) of eEye's analysis aside (why they haven't identified on the XMPlay vulnerability is another question), users need to be aware that if they replace WMP with XMPlay as the default handler of .asx content, then they are potentially creating a much riskier environment than if they accept the current DoS risk against their platform.

    If this particular code release had appropriate accompanying documentation, it would be possible to work out whether it is a derivative of the earlier code, or fortuitous timing on something found independently.

    Criticism has been recently levelled against third party reporting bodies for failing to adequately investigate reports (after one of the recent MoKB OS X corrupted .dmg file handling errors), and the way that information is flowing between, and being distributed by, third party reporting bodies in this case is showing similar patterns.

    In summary:
      - There is a known 0-day targeting a vulnerability in XMPlay's handling of malicious .asx (and other content types) data passed via 'ref href' that can lead to arbitrary code execution.
      - There is a known DoS targeting WMP that is exploited via a long string passed via 'ref href' and using the .asx media type
      - There has been no proven link between the two disclosures
      - It has yet to be shown that the WMP vulnerability leads to arbitrary code execution
      - The advice to replace WMP as the default .asx filetype handler can lead to an increased security risk if the replacement application is XMPlay (accepting arbitrary code execution in an effort to avoid a DoS).

  59. What is happend? by Anonymous Coward · · Score: 0

    So, Tomorrow we will see yet another hole on the m$ products, but the micro$oft will said "hey folks! use the vista instead" and all the lemmings will be happy ;)

  60. It's Been Merry Since Easter by SkiifGeek · · Score: 1

    If you look at the history of .asx file exploitation, there has been malware in the wild targeting various .asx vulnerabilities since at least Easter this year. This particular issue was publicly disclosed on November 22, and was only a DoS at the time. There are suspicions that it is a derivative of other code published publicly the day before, which targeted the XMPlay player (the exploits are very, very, very similar).

    Either way, it probably won't see much of a change, though it is disappointing to see all the 'respected' InfoSec companies suckered in by eEye's dubious description (concerns have been raised on at least one security mailing list).

  61. Message from Java to C++ by Anonymous Coward · · Score: 0

    Start using String classes. We're sick and tired hearing of these 'buffer overflows' as you call them.

  62. How much of userland runs in ring0? by Anonymous Coward · · Score: 0

    With MS code, a shedload. Much of IE, lots of graphic code, several applications (like ping, apparently).

    Userspace drivers NEVER run in ring0. That is why they are CALLED userspace drivers.

    MS will never push drivers to Ring3 because there needs to be a context change every time the kernel changes to the driver. That was why NT started slow by damn secure and got worse: drivers weren't in the kernel and MS wanted better performance and damn the consequences.

    1. Re:How much of userland runs in ring0? by Anonymous Coward · · Score: 0
      MS will never push drivers to Ring3 because there needs to be a context change every time the kernel changes to the driver
      Yeah, so don't expect graphics to go ring 3 in gaming/home user versions of windows but there's no reason why it shouldn't on servers. Various other drivers where high performance isn't needed can likely be moved there too, especially now CPUs are so fast. It could probably even be made configurable by supplying drivers in both rings and letting the user choose which ones to enable.

      Also it's a myth that IE runs ring0, sure it's proven full of userspace exploits in the past that tend to own the machine, but this is largely because everyone runs as Administrator (and because the security 'zones' were poorly implemented.)
    2. Re:How much of userland runs in ring0? by Anonymous Coward · · Score: 1, Informative

      Actually, the Windows Display Driver Model (WDDM) in Vista does move the majority of the video driver into ring3. Without the WDDM driver you don't get the fancy-pants accelerated UI. A lot of people focus on the obvious improvements in Vista, which are few, but there are a lot of underlying changes which will move to fundamentally overhaul the platform. WDDM is one of them. Combined with the DX10 requirements for graphics cards they will soon have all of the scheduling and memory management features as the CPU.

      http://www.hardocp.com/news.html?news=MTkyNzgsLCxo bmV3cywsLDE=

  63. Zero day ? by nstlgc · · Score: 1

    The fact that "a zero day flaw has been reported" somewhat gives me the impression that neither the submitter nor the editor know what "zero day" refers to. Or perhaps it's just another example of the media hyping a word to a level where it has no meaning anymore.

    Last time I checked, "zero day" referred to how many time had passed since the was discovered, released, ...

    As in " y0 du0dz eye gotz th1s m4d 0d4y expl0it from 7350, th1s isnt ev3n on hack.co.za y3t!"

    [Disclaimer: references in quote might only be obvious to dinosaurs.]

    --
    I'm Rocco. I'm the +5 Funny man.
  64. Oh, So Happy It's Thursday by wowbagger · · Score: 3, Funny

    Microsoft had two
    Oh
    So
    Happy
    It's
    Thursday
    moments this week so far: Tuesday's 0-day in Word (which has an exploit) and this one Friday (which currently does not have an exploit).

  65. doesn't affect my Vista machine .. by rs232 · · Score: 1

    What exactly is misleading about the post. Is there *not* a zero day bug in Windows Media player. Does it not relate to WMVCORE.DLL.

    "Doesn't affect my Vista machine. Nor my XP Pro machine running IE7 + WMP 11"

    What version of WMVCORE.DLL does WMP 11 use and is there a security advisory saying XP is not affected.

    ""the function at 7D7A8F27 in WMVCORE.DLL version 9.0.0.3250, and at 086E586E in WMVCORE.DLL version 10.0.0.3802"

    ""I can't help but wonder what it might look like if every time a flaw was discovered in *Nix, and a security advisory .. were released,and slashdotted"

    Slashdot has been known to mention bugs in Linux.

    "How often does a kernel update in Linux break something that you now have to update, or sometimes roll back alltogether because they won't work"

    It doesn't as you aren't forced to update the kernel. Even if you do you can have multiple versions. The same with the apps. And you would never do a major upgrade on a production machine.

    was GG Misleading Post (Score:5, yet another Winpologist getting modded up Insightful)

    --
    davecb5620@gmail.com
  66. Re:WMP11 EULA Time Bomb by Crayon+Kid · · Score: 1

    If you insist on only seeing a small part of the DRM picture, specifically the one that doesn't affect you and your files now, you will be all the more surprised when the ugly side of DRM hits you at some point in the future. Except by then it will be too late to do anything about it.

    I speak as a person who has been hit by it several times already. And you are affected too, if you'd be willing to open your eyes. What if you want to listen to the CD on the computer and you're told you may not do that? How is that fair?

    --
    i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
  67. zero day potentially exploitable flaw .. by rs232 · · Score: 1

    "Since when did a "potentially exploitable heap buffer overflow" become a zero-day exploit?"

    Happy now :)

    was zero-day exploit (Score:4, lets not talk about the potential flaw)

    --
    davecb5620@gmail.com
  68. Does it surprise you? by cj5 · · Score: 0

    Not me. Same crap different operating system version. Same thing happened with the introduction of XP. All kinds of exploits, worms, viri, exploded onto the scene of Microsoft's earlier OS products, applications which already had fixes. Then all of a sudden one application is susceptible to hacks. It's all a marketing scam by Microsoft, because they figure most dimwits who use their products will get infected, and think that the OS doesn't work anymore, because it's an old version, so they buy the "new" and "improved" Vista. A sucker is born every second.

  69. Like searching for hay in a haystack. by singingjim · · Score: 0

    In all these types of "exploits" it seems as if Mars has to be aligned with Jupiter and the moon has to be rising over Uranus before something really bad can happen. Just more nonsense that 90% of users can ignore. The other 10% probably deserve to get hacked. Risk will always be a part of life. Evolution will keep the herd strong by letting the idiots get eaten/hacked.

    --
    Terrible karma and aiming lower, which in this environment of one-sided reason, is higher.
    1. Re:Like searching for hay in a haystack. by Anonymous Coward · · Score: 0

      > In all these types of "exploits" it seems as if Mars has to be aligned with Jupiter
      > and the moon has to be rising over Uranus before something really bad can happen

      That's Microsoft's technical writers earning their daily bread. Strip out all the manipulative language from that part of your average Security Bulletin Summary which describes the threat - that language which has been put in to create the emotion in the end-user that you just expressed, i.e., that likelihood is remote, and you have to have the stars aligned in a highly improbable constellation - and the "exploits" are not only disarmingly simple and straightforward to explain (which, btw, would be a great thing to start happening to those SBSes), but the supposed hurdles an evil unknown hax0rr has to overcome to pull it off start to look no higher than a fried egg.

      Now, maybe x out of ten exploits really are a Sisyphusian task to make happen on your desktop -- but you don't really know until you read some chatter from folks not on Microsoft's payroll, at which point you can decide whether things apply to you or not.

      The other problem with the corporate-slimeball language in MS' SBSes - that in 2006, they shockingly reinforce the silly silly idea that computer security is proportional to your only choosing to communicate with people you "know" and "trust" - is the way it reinforces the most primitive (and thus, easily accepted) superstitions. You may know and love and trust Mary B., and respect her leet skillz, but exactly how that translates into "Any .DOC I receive from HER is OK to open!" is still beyond me. "Security" education for the masses really needs to get closer to the point that AIDS education has gotten: the idea that it's the barrier and not the carrier.

      Because that superstitious discussion parading as "security strategy" is taking place right in this topic, on this page. Jeez.

  70. Mod parent redundant... by M00TP01NT · · Score: 2, Funny

    Could have sworn parent made this same comment a few moments ago...

  71. Re:You Could... by mingot · · Score: 1

    There is nothing new about strncpy().

  72. Re:WMP11 EULA Time Bomb by ConceptJunkie · · Score: 1

    What if I simply choose not to use software that acts like that?

    DRM isn't going to stay or go away based on anything I do, and I'm not affected by it, nor will I be upgrading to Vista or WMP11 or any of the other crap being excreted by Microsoft.

    DRM can't affect you if you don't invite it on to your hardware.

    --
    You are in a maze of twisty little passages, all alike.
  73. Re:WMP11 Has Serious Exploit by SydBarrett · · Score: 1

    In WMP11 and previous versions, there is an option to not copy protect music. It's just one checkbox. Or you can not use the WMA format and use mp3 or whatever. Or you can not use WMP at all.

    I have no idea about how DRM in cable works though. I record all my shows using a VCR because it's analog and the shows look warmer than using digital recording.

  74. Re:You Could... by koh · · Score: 1

    I think the GP refers to the new "secure" string functions in the VS2005 CRT API, such as strncpy_s (or _tcsncpy_s if you're into unicode).

    --
    Karma cannot be described by words alone.
  75. Re:WMP11 Has Serious Exploit by Anonymous Coward · · Score: 0

    This is FUD. WMP11 doesn't automatically add DRM to your music collection. It will only add DRM to files you RIP with the DRM option on. A feature that's been in WMP for years. This option defaults to OFF as well.

    To Summarize:
    1. WMP11 does not, in any condition, add DRM to any unprotected files that already exists.
    2. WMP11 does not, by default, add any DRM durring the ripping process unless you tell it to.

  76. no version, no POC, selling their 'solution' by dioscaido · · Score: 1

    It's lame that something like this makes the front page. The report makes no mention of version, no proof of concept code is available. Ah but they DO try to sell your their security application which supposedly protects from this vulnerability.

    1. Re:no version, no POC, selling their 'solution' by figleaf · · Score: 1

      It does mention the file versions. From the fileversions you can determine that WMP9 & WMP10 can "supposedly" be exploited.
      WMP11 doesn't have the issue.

    2. Re:no version, no POC, selling their 'solution' by dioscaido · · Score: 1

      Thanks! I missed that specific data.

  77. Re:WMP11 EULA Time Bomb by that+this+is+not+und · · Score: 1

    Didn't you know that DRM hides under your bed at night. It's the boogieman and completely unavoidable. You can pretend that there isn't a Windows Media Player version in your future, but there it is staring you in the face.

    Personally, I have just decided to never install any Windoze newer than the Windows 2000 that I keep running on my last Windows desktop machine. W2K was a plateau for Microsoft, and anything newer than that is loaded down with capracious malware. 'Validate' every reinstall? No way.

    Windoze does have it's place. I use a W98 laptop as my development platform for PIC controllers. It's certainly not a 'platform of the future' however.\

    People are gradually figuring it out.

  78. Re:WMP11 EULA Time Bomb by ConceptJunkie · · Score: 2, Insightful

    The problem is that for more than a decade Microsoft's priorities have been:

    1. Maintain their monopoly
    2. Fool the government into thinking they don't have a monopoly
    3. Enforce Microsoft lock-in to existing customers
    4. Spreading FUD about Linux and Open Software in general
    5. Band-aiding the constant stream of security flaws in their older products
    6. Inventing more and more byzantine and fragile DRM schemes that are still hacked before they are even released
    7. Making new software people actually want to use

    As you can see, making good software gets trumped by everything else. As far as I'm concerned, they could have stopped with Windows 2000 and stuck to releasing new hardware support, bug fixes and security patches, and we would all be a lot better off.

    Can you imagine how lean, mean, secure and smooth a "Windows 2000 Service Pack 11" would have been in 2006?

    It would be everything Microsoft spend 5 years failing to deliver with Vista.

    --
    You are in a maze of twisty little passages, all alike.
  79. Automatically launching is inherently insecure. by jonadab · · Score: 1

    I had to google ASX to find out what it is, but the first result (which seems to be advocating their use, incidentally) says this:

    > ASX files are textual command files that manage [something]. They are very
    > small in size (about 1K) because they contain no data, just instructions.

    Now, I don't know the technical details of the format, but if that statement is straightforwardly true, then automatically launching these files is inherently a complete abdication of all pretense of security, and any application (be it a mailreader, a web browser, or a desktop application) that automatically launches just any old .asx file it happens to run into is inherently totally insecure.

    I don't mean just risky. I mean totally stupidly insanely dangerous.

    Automatic launching of *anything* is risky, even if it's just data (e.g., a PNG image), because you don't know what vulnerabilities the app that handles the format might have (e.g., buffer overruns and so forth). But when you automatically launch *instruction* (as opposed to data) formats, the risk that you have introduced an exploitable vulnerability is practically always 100%.

    It's a cardinal no-no. You don't *EVER* program an app to automatically launch executable code like that. This is not your garden variety programming mistake that introduces the potential for insecurity. This is Grade-A Fancy insecurity, served on a golden platter to the bad hats.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  80. It's called... by d3ac0n · · Score: 1

    Use WINAMP!

    The new versions of Winamp will play any file that WMP Plays. That, combined with WMP Classic, QT Alternative, Real Alternative, and The Matroska codecs and I'm all set. Heck, my XP box is still running WMP 9! I just dissassociate it with all files, and then stop using it. I never need to touch it again after that.

    My Ubuntu box will also play any of the above thanks to Easy Ubuntu. I just loaded up what I wanted, and away I go. (although I wish Amarok was available for the Gnome interface. I hate Totem.)

    --
    Official Heretic from the "Church of Global Warming". Proven right thanks to whistle blowers. AGW = Flat Earth Theory
    1. Re:It's called... by Anonymous Coward · · Score: 0
      Use WINAMP!
      ...and just what is Winamp sending to AOL on every startup? (even if auto-update checks are disabled)

      Winamp died as a usable application when Nullsoft sold it to AOL. It simply cannot be trusted.

      Hopefully Nullsoft will never sellout NSIS.

      P.S. I changed my IP address to make this post as this is getting a bit ridiculous:

      Slow Down Cowboy!

      Slashdot requires you to wait between each successful posting of a comment to allow everyone a fair chance at posting a comment.

      It's been 26 minutes since you last successfully posted a comment


      26 minutes? Sheesh, pretty excessive flood control, even for mod_perl... hehe.
    2. Re:It's called... by Anonymous Coward · · Score: 0

      You can use AmaroK in gnome, in fact i am right now.

  81. Does Windows now come in Spray Cans? by abb3w · · Score: 1

    If you insists on comparing MS security with a cheese product, then compare it with foam-cheese

    Something vaguely cheesy, that has more holes than substance? Works for me....

    And if you had left off the smiley, you probably would have gotten the +5 as "Insightful" instead of "Funny".

    --
    //Information does not want to be free; it wants to breed.
  82. Re:Let's Stop With This 0-Day Shit by Overly+Critical+Guy · · Score: 1

    Whoa, it's Steve Ballmer! How are those squirting Zunes selling?

    --
    "Sufferin' succotash."
  83. Re:Fix found for zero day flaw by Anonymous Coward · · Score: 0

    We really don't give a shit anymore if Joe Average can use or figure out Linux. Joe Average can drive his SUV straight off a fucking cliff with a Budweiser in his hand for all I care.

    If Joe Average ever gets a clue, he can switch to a Mac. Leave Linux to the geeks and be done with it, it's not meant to be a general usage desktop OS for the Average Joes of the world.

  84. Exploits in media players by tacokill · · Score: 1

    Is it just me or does anyone else wonder why a MEDIA PLAYER is even exploitable? Why is it so hard to secure an application that plays/views data files. Can't you build in some limitations to prevent this problem? I mean, after all, it's nothing more than a "viewer" of data files (streamed or local). MSFT continues to add "functionality" to it's media player and now they are reaping what they sow. Media players don't need scripting and all the other "functionality" MSFT *thinks* we need. Just play the damn file, thank you very much.

    Seems like with ever iteration of MSFT Media Player, more exploits come to fruition. I miss my media player ver 6.4, which was simple and convenient.

    Since ver 6.4, media player has become a steaming pile of doo-doo. Hell, I can't even open multiple video windows with MP 10 and MP 11. It's like we are going backwards with these things....and the exploits just add fuel to the fire.

    Sorry, I just had to get this off my chest. Its been a peeve of mine for a long time (and yes, I now use VLC)

  85. Re:Fix found for zero day flaw by kurt555gs · · Score: 1

    Interesting , he actually has a point.

    cheers

    --
    * Carthago Delenda Est *
  86. Re:WMP11 Has Serious Exploit by Pusene · · Score: 1

    I have no idea about how DRM in cable works though. I record all my shows using a VCR because it's analog and the shows look warmer than using digital recording.

    Hope you didn't tape Ice Age...

    --
    Error #13: No coffee. Operator halted. Please place boot device at bottom.
  87. Microsoft's Solutions? by Master+of+Transhuman · · Score: 1

    Well, for Word, they suggested not opening or saving Word documents.

    That's one app down.

    I suppose for the Player, they suggest...not playing anything.

    Another app down.

    What's left? Excel? Access? We already KNOW Outlook Express and Outlook and IE are toast on a daily basis.

    And corporations still USE this crap?

    Suckers.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  88. WRONG NEWS, because the fix is already avaible!!! by terrz · · Score: 1

    WRONG NEWS, because the fix is already avaible!!! You have just to install the latest Windows Media Player 11 that is not affected by this flaw!