Slashdot Mirror


New Linux Worm Found in the Wild

randomErr writes "The worms, Slapper.B and Slapper.C, which exploits a known buffer overrun vulnerability in the Secure Sockets Layer 2.0 (SSLv2) handshake process has infected thousands of Web servers worldwide, according to Helsinki-based F-Secure Corp., a computer and network security company. "

9 of 366 comments (clear)

  1. Wow! by Anonymous Coward · · Score: -1, Offtopic
    I actually got a first post!!! Woohoo!!

    Click here

  2. Rather Than A First Post by Anonymous Coward · · Score: -1, Offtopic

    I'll just wait for first reply

    1. Re:Rather Than A First Post by Anonymous Coward · · Score: -1, Offtopic

      Hey!

      I'm first reply!

  3. True by Anonymous Coward · · Score: -1, Offtopic

    The true story of slapper is here

  4. Re:Finally by aivic · · Score: 0, Offtopic

    Linux can be utilized as a Desktop OS!

    I can do everything virtually in Linux what I can do in Windows.

    Theres only little in the field of capturing/encoding divx movies and graphical download managers, but I might be wrong there since I havent bothered to look.

    I also have to give a lecture on the slapper worm in a couple weeks and I havent really started my presentation notes :(

    Wish me LUCK!

  5. IF I EVER MEET YOU I WILL KICK YOUR ASS!!! by Anonymous Coward · · Score: -1, Offtopic
    1. Re:IF I EVER MEET YOU I WILL KICK YOUR ASS!!! by Anonymous Coward · · Score: -1, Offtopic

      WHO SAID THAT?!

  6. Great. by Anonymous Coward · · Score: -1, Offtopic

    Slasdot the mail lists with more mindless questions again!

    Wanna bet you get 10 new emails from your (insert company)securitymailing-list from mindless F--k's with questions about how long for a patch for the "NEW" worm?

  7. I've never understood... by HarryLeBlanc · · Score: 0, Offtopic
    ...why buffer overflow viruses are such a common vulnerability in software. Yes, I grok how they work, but their effectiveness depends on knowing in advance exactly how big the buffer is.

    It would be trivially easy to write a function to randomly assign buffersize based on parameters (say, min max and optimal size), and even change its size periodically at runtime. That would eliminate this entire class of attack.