SMB Security Hole
Thangorodrim writes "First saw this at
SecurityFocus, but it seems as if someone at COTDC finally got around to coding a nice SMB session hijacker for NT/2000. I've tested this on some machines...its pretty brutal. And just in time to coincide
with the release of l0phtcrack 3.0... The story linked doesn't have a link to the actual utility, but you can grab it here." *cough* For testing purposes only, of course.
well, even with the crappy security that's become the norm with msft products, an os using a nt kernel will always be more secure than an os using a 9x kernel.
even if nt's implementation is flawed, it at least has the design, like users, permissions, and some seperation of kernel- and user-space.
with that said, a default install of nt (dunno about win2k, never touched it) is so horrible that it brings the overall security of the system almost down to the win9x level. which is to say none at all. come on, who besides msft would ship a product with the filesystem permissions blown wide open by default?
but the moral of this story is: don't use default installs on production systems. even if they aren't windows.
---
How does samba avoid this hole? (Better design in the first place? Or saw the problem and fixed it?)
Daniel
As win2k "ages" it seems as though more and more holes in it are being found. Could this eventually make win2k as unsecure as Win9x?