|
Joe,
Port 135 may be open, but this patch does not allow the
same exploit that blaster/nachi used. The BoF that was exploited is
closed, so the port being open is only a RPC port - until the next vuln is
found.
Rick Kingslan MCSE, MCSA, MCT From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pelle, Joe Sent: Thursday, September 11, 2003 10:25 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] New RPC DOS I’ve noticed that once
this new patch is applied Joe
Pelle Systems
Analyst Information
Technology Valassis / Targeted
Print & Media Solutions Tel
734.632.3753 Fax
734.632.6240 This message may have
included proprietary or protected information. This message and the
information contained herein are not to be further communicated without my
express written consent. From: Salandra,
Justin A. [mailto:[EMAIL PROTECTED] But if you use applications like Outlook
with Exchange 5.5 then you can’t
communicate. -----Original
Message----- The
solution is to do away with RPC entirely - but that's a major rewrite of things.
On the other hand, I have plenty of Unix boxes running with RPC disabled and
they run fine. Let's
remember RPC's major functionality can be replaced, but that's at the expense of
more complex application design. Roger -------------------------------------------------------------- -----Original
Message----- Todd, >> Anyone have a
clue as to how Microsoft plans to fix the RPC system to make it more
secure? Concentrate maybe one
or two more people on looking at error checking on the input into the
arrays/buffers in the RPC code? ;op I mean, really - a vuln
lays around waiting for someone to find it for years, and in this short of a
time 3 more vuls are found in roughly the same area, just different
vectors? I sure hope that there is a team pouring over the code that makes
up RPC. Rick
Kingslan MCSE, MCSA, MCT From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Myrick, Todd
(NIH/ Our Microsoft
At I think it is very
important to get this update on all your DC's even if they are behind a firewall
ASAP. We managed to mitigate blaster but these RPC DOS are starting to get
really nasty. Anyone have a clue as
to how Microsoft plans to fix the RPC system to make it more
secure? Thanks, Todd
Myrick |
Title: Message
- [ActiveDir] New RPC DOS Myrick, Todd (NIH/CIT)
- RE: [ActiveDir] New RPC DOS Rick Kingslan
- RE: [ActiveDir] New RPC DOS Roger Seielstad
- RE: [ActiveDir] New RPC DOS Salandra, Justin A.
- Re: [ActiveDir] New RPC DOS Andy David
- RE: [ActiveDir] New RPC DOS Pelle, Joe
- RE: [ActiveDir] New RPC DOS Rick Kingslan
- RE: [ActiveDir] New RPC DOS Bendall, Paul
- RE: [ActiveDir] New RPC DOS Ken Cornetet
- RE: [ActiveDir] New RPC DOS Bendall, Paul
- RE: [ActiveDir] New RPC DOS Michael B. Smith
- RE: [ActiveDir] New RPC DOS Roger Seielstad
- Re: [ActiveDir] New RPC DOS Glenn Corbett
- RE: [ActiveDir] New RPC DOS Rick Kingslan
- Re: [ActiveDir] New RPC DOS Glenn Corbett
- RE: [ActiveDir] New RPC DOS Mulnick, Al
- RE: [ActiveDir] New RPC DOS Roger Seielstad
