main

Flaws expose Windows Server 2003

Sleeper   on 01 July 2003 - 15:05 · 9 comments & 1830 views

Advertisement (Why?)
Windows Server 2003 shipped in April with drivers afflicted by the Etherleak bug, first identified in January

Several third-party device drivers that ship with Windows Server 2003 contain a vulnerability that causes them to leak potentially sensitive data during TCP transmissions.

Security experts have criticised many of the vendors for failing to act quickly enough to guide users to fixes, and said the flaw could lead to attacks through local area networks (LANs).

The so-called Etherleak flaw, first highlighted in January, occurs when messages transmitted between two machines are padded with arbitrary data in order to bring their byte size in line with the accepted standard. When Ethernet frames do not meet the minimum size requirement specified by the standard, the device drivers pad the frames with data pulled from previously used buffers. This means that whatever information was in that buffer is then sent as part of the new transmission.

News source: vnunet.com


Researchers from security consultancy NGSSoftware said the problem was at its worst during the closure of a TCP connection when the FIN and ACK packets are exchanged. During such exchanges, the researchers were able to observe email passwords.

Chris Taget, a senior security consultant at NGS Software, said that the vulnerability could be extremely serious to firms. "If you are running a web server on the internet it will not be a problem, but if you are running a server containing sensitive data on a local network which other people are on, it could be a big problem," he said. "Users on the same LAN could receive passwords and sensitive information about the server."

He said that if firms were in doubt they should contact their network card vendors immediately. "IT directors should find out if their vendors have updated the driver to resolve the issue," he said. "The problem is that many vendors have not contacted [security advisory body] Cert to declare whether their products are vulnerable or not."

Taget said Microsoft had been in a no-win situation when certifying third-party drivers for Windows Server 2003. "Microsoft is now getting flack for signing off third- party drivers, but would also get flack for refusing to certify drivers that support hardware," he said.

There are several drivers affected by the TCP version of this vulnerability, including those for Advanced Micro Devices PCNet network cards and Via Technologies Rhine II-compatible network cards, according to a bulletin from NGSSoftware. Both of these drivers are digitally signed by Microsoft and are included on the Windows Server 2003 installation CD.

The news followed last week's release of the first patch for Windows server 2003 to plug a flaw in Internet Explorer 5.01, 5.5 and 6 on all Windows platforms, which could allow the execution of malicious code on a vulnerable machine. Microsoft assured customers that the operating system itself is still sound and the bug is in a related application rather than in the operating system itself.


Post a comment · Send to friend Comments · There are 9 additional comments
(2 replies) #1 Quick Reply on 01 Jul 2003 - 15:13
who the heck is Sleeper? i've never heard of the newsposter before
#1.1 creamhackered on 01 Jul 2003 - 15:22
He's been here for aslong as I can remember but has been off for a while. Thanks for welcoming him back so nicely
#1.2 Quick Reply on 01 Jul 2003 - 15:24
It's all good now, Welcome back to Neowin!
#2 JaggedFlame on 01 Jul 2003 - 15:18
QUOTE
Taget said Microsoft had been in a no-win situation when certifying third-party drivers for Windows Server 2003. "Microsoft is now getting flack for signing off third- party drivers, but would also get flack for refusing to certify drivers that support hardware," he said.


Trudat. WHQL has been a bit of a joke lately.
#3 budwizer on 01 Jul 2003 - 15:45
Isn't this old news? The date on the article on vnunet is 6/13/03:

http://www.vnunet.com/News/1141582
http://www.neowin.net/comments.php?id=11708
http://www.infoworld.com/article/03/06/09/HNleaky_1.html
(2 replies) #4 vettimdorr on 01 Jul 2003 - 16:21
wtf, why not pad the extra data with 0's?
#4.1 hao2lian on 01 Jul 2003 - 16:58
Because then we can't poke fun at Microsoft anymore.
#4.2 Jugalator on 01 Jul 2003 - 17:08
I also asked myself this question. Just allocate a buffer to fill the remainder and zero it out. I have a feeling there's more to it than this problem, since it just seems like a *too* stupid and easy to fix flaw that it have stayed since january.

It's even common programming practice to zero out buffers before usage.
#5 Mr. Black on 01 Jul 2003 - 16:25
Too many flaws...

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)