Hello,

Am Donnerstag 15 Mai 2008 schrieb Jan-Oliver Wagner:
> Hello,
>
> (I am CCing this to openvas-plugins, the mailing list for plugin issues)
>
> On Mittwoch, 14. Mai 2008, Vincenti Francesco wrote:
> > I am writing you to understand the correct behaviour I should have in
> > front of the results of OpenVAS scansion, according the following
> > "problem".
> >
> > Every scansion of my company's PC I have done until now shows a security
> > hole in each machine which is detected by plugin 11808, about Microsoft
> > RPC Interface Buffer Overrun, and is caused by epmap on port 135.
> >
> > The plugin suggests to update the operating system to a kind of patch
> > but when I try to install it the answer is that the operating system
> > version in more recent than the patch itself: obviously, the problem is
> > known since 2003 and Windows has reached the SP 2 now!
> >
> > Is this result the consequence of some missed update of the plugin 11808
> > or is the pluging itself which is not update to the SP 2, and how can I
> > solve this false positive?

I've tested against XPSP2 and there was no warning for me.

> >
> > Thank you very much for your attention.
>
> I am not a plugin developer nor would I call myself a Windows guru.
>
> However, the first observation when looking into the NASL code
> (msrpc_dcom.nasl) is that a dependency is not fullfilled
> (msrpc_dcom2.nasl). This script is missing which is probably because it is
> kept proprietary by Tenable (OpenVAS project obviolusly had to remove any
> proprietary elelement).
> But this does not necessarily cause the problem.

I've taken a look to this script. Probably the dependencie is only related to 
the KB Test at the begin of the script.

>
> I can try to reproduce the problem, but I'd need to know how to start
> the service at port 135. My default XPSP2 has nothing running there.

Port 135 is the RPC (Remote Procedure Call) Port and is normally open on every 
Windows. Without this Service Windows is probably not working correctly. If 
you do not see this Port on Portscanning this will normally meen you have 
activated a firewall. Try this "netstat -na -p tcp" on a commandshell in 
Windows and search for "TCP 0.0.0.0:135   0.0.0.0:0 listening" or so in the 
result.
If you not find this, take a look to the Services. There is a Service named 
Remoteprocedurecall (RPC) or in german "Remoteprozeduraufruf (RPC)" which 
normally should be running.  OK but this is not the question i think.
The Script 11808 is sending some binary stuff (probably initiating a rpc 
session) to port 135 and is looking for a special answer or better if the 
answer is NOT one of this 
chk[1] = raw_string (0x00,0x05,0x00,0x07);
chk[2] = raw_string (0x00,0x00,0x20,0x00);
chk[3] = raw_string (0x02,0x00,0x01,0x00);
and is then raising the warning. 
It is very likely this is a false positive.

Very interesting to me is, that this script will give me no warning if i run 
it by openvasd but if i run it by openvas-nasl and DEBUG=1 within script i'll 
get this warning. But anyway i'm very sure this is a false positive on newer 
XP/2003 OS.


Gruss
    Carsten Koch-Mauthe
    
 http://www.dn-systems.de  mail: [EMAIL PROTECTED] 
 DN-Systems Enterprise Internet Solutions GmbH
 Hornemannstr. 11 31137 Hildesheim, Germany     
 Tel. +49-5121-28989-0 Fax. +49-5121-28989-11 
 21 Sunrise Ct, S.San Francisco, CA 94080, USA
 Tel. +1-650-472-2512  Mob. +1-650-430-1219
 Handelsregister HRB-3213 Amtsgericht Hildesheim
 Geschäftsführer Lukas Grunwald
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to