Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX
From: Hector Santos (nospam@nospam.com)
Date: 03/31/03
- Next message: \: "Re: THESE ARE SIGNS TO LOOK FOR TO TELL YOU YOUR COMPUTER IS HACKED/OWNED"
- Previous message: Lars M. Hansen: "Re: THESE ARE SIGNS TO LOOK FOR TO TELL YOU YOUR COMPUTER IS HACKED/OWNED"
- In reply to: S. Pidgorny [MVP]: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Next in thread: x y, mvp: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Reply: x y, mvp: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Hector Santos" <nospam@nospam.com> Date: Mon, 31 Mar 2003 07:12:16 -0500
I just wrote to the FBI about this:
Dear FBI:
This is not a direct link to 911, but I think the FBI needs to put pressure
on Microsoft to fix a major security FLAW on Windows NT 4.0. Microsoft has
recently announced they will not address the recently
found RPC Security flaw on Windows NT 4.0. Only Windows 2000/XP will be
addressed. Over 75% of the market place still uses Windows NT 4.0,
including our organization. We were attacked by Russian Hackers back in
1999 and we were among the first computer crimes cases for the newly
established North Miami FBI Computer Crimes Division. So I am very
sensitive and concern about security issues. It is a nightmare to be
terrorized by computer hackers. Microsoft is a signicant entity in the
computer industry. If Microsoft is allowed to "relax" its responsibility to
address security flaws, this makes our entire country vulnerable to hackers
world wide. The last major virus epidemic that effected
Microsoft Windows was Code Red. The major significance of this virus was
not its uniqueness, but the fact that it relied on the majority of our
nation's computers are using vulnerable Microsoft Software. I'm
afraid another similar virus episode of major proportions if Microsoft does
not address this Windows NT 4.0 flaw.
Please make a public statement that Microsoft MUST address this security
flaw as a National Security measure as soon as possible.
Thank You
Sincerely
Hector Santos, CEO/CTO
Santronics Software, Inc.
"S. Pidgorny [MVP]" <slavickp@yahoo.com> wrote in message
news:u4y1In29CHA.1808@TK2MSFTNGP12.phx.gbl...
> Hector,
>
> Microsoft follows supposedly open DCE specifications for RPC and some
other
> DCE protocols (Outlook/Exchange TNEF). Hardly local RPC (LRPC) requires
open
> port for endpoint on the network interface.
>
> I work for organisation that runs several hundred NT servers despite
> significant effort to upgrade. I don't like MS not fixing the
vulnerability
> and the way it's made official. However I understand that Microsoft cannot
> support all the versions forever. I don't hear complaints about NT 3.51
not
> being fixed...
>
> --
> Svyatoslav Pidgorny, MS MVP, MCSE
> -= F1 is the key =-
>
> "Hector Santos" <nospam@nospam.com> wrote in message
> news:OihQ$T29CHA.2376@TK2MSFTNGP10.phx.gbl...
> > I am extremely disappointed Microsoft has decided not the fix NT 4.0 RPC
> > Endpoint Mapper flaw. I am highly skeptical it not being done due to
> > "architectural limitations." Hogwash. I don't buy it. I will be
> > interested to see the reaction among my own customer base still using NT
> > when "told" they must upgrade to W2K or XP.
> >
> > Until this is settle, Microsoft must be open to releasing technical
> > information about the flaw to see if developers who are dependent on RPC
> > operations can provide a fix on their own.
> >
> > Specifically, our RPC client/server product do not use the Endpoint
Mapper
> > so I need to see if its possible to provide a workaround to customers to
> > simply tell them to block port 135. However, I'm afraid point 135 may
be
> > used internally by RPC for more than just end point mapping. This is
the
> > type of info I need to know from a technical standpoint to see what
steps
> > need to be taken.
> >
> > Does Microsoft provide technical RPC specifications somewhere?
> >
> > ----
> >
> >
> >
>
>
- Next message: \: "Re: THESE ARE SIGNS TO LOOK FOR TO TELL YOU YOUR COMPUTER IS HACKED/OWNED"
- Previous message: Lars M. Hansen: "Re: THESE ARE SIGNS TO LOOK FOR TO TELL YOU YOUR COMPUTER IS HACKED/OWNED"
- In reply to: S. Pidgorny [MVP]: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Next in thread: x y, mvp: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Reply: x y, mvp: "Re: Flaw in RPC Endpoint Mapper - NT 4.0 FIX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
