RE: Exchange 2k hacked

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 27 Oct 2003 16:45:49 -0500

The DCOM access issue may be "normal" for that environment and indicative of
some other previous problem or even none at all (could be a security setting
too tight for all I can tell here), but my personal thought is that if you
have any questions or doubts, you'd be best served by being safe and
rebuilding.  That's my idea of best practice anyway.


From: Mark Hippenstiel [mailto:M.Hippenstiel@xxxxxxxxxxxx] 
Sent: Monday, October 27, 2003 4:03 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange 2k hacked

Today I had to resurrect an exchange 2k server that had relaying for
successfully authenticated hosts allowed. This wouldn't have been a problem,
had the user 'webmaster' had a password assigned :) I guess this was some
left-over from a previous Novell migration. Well. I cleared out half a
million spam emails.

What got to me was the presence of a process named unsecapp.exe which I have
not noticed running anywhere before. A quick google returns some references
to event sinks. Further, there have been various dcom errors, stating an
access error while starting a {3Dxxxx... application. All this could be
perfectly legit, but I want to make sure that this host has not been
tampered with. 

The exchange is running behind ISA and has only SMTP published. The SMTP
vuln had been fixed on the 24th I think. Any clues?


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:

Other related posts: