Slashdot Mirror

← Back to Stories (view on slashdot.org)

XP/Vista IGMP Buffer Overflow — Explained

Posted by kdawson on from the that-didn't-take-long dept.

HalvarFlake writes "With all the hoopla about the remotely exploitable, kernel-level buffer overflow discussed in today's security bulletin MS08-0001, what is the actual bug that triggers this? The bulletin doesn't give all that much information. This movie (Flash required) goes through the process of examining the 'pre-patch' version of tcpip.sys and comparing it against the 'post-patch' version of tcpip.sys. This comparison yields the actual code that causes the overflow: A mistake in the calculation of the required size in a dynamic allocation."

1 of 208 comments (clear)

  1. Why Windows 95 and NT 4 are enough by Anonymous Coward · · Score: -1, Offtopic

    Why upgrade?

    I don't plan to upgrade from Windows 95, NT 3.51, and NT 4 on the desktop. With network booting, Windows 95/NT do everything I need for user workstations. Of course, I run OpenBSD on the server. Modern graphical user interfaces are mess. Even modern versions of X are very bloated. And don't get me started on mainstream window managers.

    Microsoft should go back to Windows 95's user interface. Combine it with NT and add a good command line shell with SFU. That would be perfect for end users. Windows 95 is actually very stable. I've had no problems supporting it for many desktops with network booting - as long as I don't install IE 5.5 and it's new Explorer.

    Microsoft should go back to fast, light user interfaces like Windows 95. Windows 95 was the best consumer operating system in 1995 (I like Apple, but Macs still had cooperative multitasking though OS 9.)

    To all IT admins: Just put all users on Windows 95. Office 97 has all the features you need. Anything else can be accessed through NCSA TELNET, SecureSHell, or even vnc.