Re: 2003 Web Server Security Flaw

From: Jeff Cochran (jcochran.nospam_at_naplesgov.com)
Date: 12/29/03


Date: Mon, 29 Dec 2003 14:43:17 GMT

On Mon, 29 Dec 2003 00:50:42 -0500, "Robert Waite"
<bob2dev@tampabay.rr.com> wrote:

>Thanks for reply.
>
>>From experience (not all forums are responsive), I posted the same question
>to microsoft.public.windows.server.security
>and got a long series of non-answers, reflexive defenses of Microsoft, and
>the simple
>answer buried deep in the answer. Please see that long **** if you are
>curious about
>the philosophy debate.
>
>Long & Short of the responses:
>1. Media Player, Netmeeting and Outlook Express are required installs for
>Web Server
> and can not be disabled/uninstalled without breaking OS.

For outlook Express, a variation on this may work:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q263837

We've removed Netmeeting on XP systems using:

RunDll32 advpack.dll,LaunchINFSection
C:\WINNT\inf\msnetmtg.inf,NetMtg.Remove

Haven't ever tried this on Server 2003.

Windows Media Player needs to be patched, but I don't know any way to
completely remove it.

>2. Their exe & dlls can not be attack points for hackers who exploit the
>on-going parade
> of buffer-over runs.

Not exactly. They may exhibit some client exploits, but in the cases
I've seen you'd have to either browse to a web site or download email
or a file to exploit any holes. Since you wouldn't normally do any of
this on your web server, you're sort of safe.

Also, you can disable file associations with these programs so even
clicking on a file on a web site won't launch them. Especially
Netmeeting, where remote desktop is disabled by default anyway.

>3. Win 2003 is great [with that I REALLY agree!]

It is, but it's a *server* and you shouldn't be vulnerable to client
attacks as long as you're not using it as a client.

At any rate, there really *should* be a lockdown option or removal
option for these utilities on a server. Unused functions should
always be disabled.

Jeff

>"Bernard" <qbernard@hotmail.com.discuss> wrote in message
>news:Ofg5JobzDHA.2528@TK2MSFTNGP09.phx.gbl...
>> You might want to rephrase you question.
>> and what is the flaw with the web server ?
>>
>> the app you mentioned can be blocked either via
>> permission or gpo restriction I believed.
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://support.microsoft.com/
>> Please respond to newsgroups only ...
>>
>>
>>
>> "Robert Waite" <bob2dev@tampabay.rr.com> ????
>> news:u1EQYzUzDHA.560@TK2MSFTNGP11.phx.gbl...
>> > Media Player, Netmeeting and possibly Outlook Express have no business
>> being
>> > on a Locked-down windows 2003 Web Server used only to host web sites,
>yet
>> I
>> > can not figure out how to un-install, or at least cripple, them.
>> >
>> > How do I do that?
>> >
>> > Thanks,
>> > Robert
>> >
>> >
>>
>>
>



Relevant Pages

  • Re: session object II
    ... web server does not hold a static connection with a client. ... Create a web service on the web server that will accept and return ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Quick Start certificate
    ... Where do I specify what the root path is. ... Then run the client. ... Did you give your web server identity permission to ... It's done through the certificate tool that's installed ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Quick Start certificate
    ... I have enabled diagnostics on the client and the web service. ... Did you give your web server identity permission to ... read the certificate on the server? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Snort as IDS
    ... The snort rules are prone to false alarms. ... you need to configure it specific to each client? ... http_inspect with any profile? ... Yes, if you are monitoring your web server, you should apply those rules. ...
    (Focus-IDS)
  • Re: Proxy Servers/Caching
    ... If this is a client issue, ... > I have tried about every cache control value on the web server. ... he said the initial request from the player has ... I'd go to IIS admin and the HTTP headers tab. ...
    (microsoft.public.windowsmedia)