On 09/21/07 08:36, Joel Elwell wrote: > I'll have to run another scan, and watch all the services as the scan leads > up to the DoS, > however the proprietary app (can't name it, sorry) is what pegs the CPU at > 99%. > Here's the services/ports based on NMAP scan.
And do you know which port corresponds to that app? Some things you might try: 1) What happens if you don't test for any SSL services? 2) How does the app react to a simple HTTP GET request (ie, "GET / HTTP/1.0\r\n\r\n") sent manually? 3) Capture packets to the affected port to see what's being sent as CPU usage spikes. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
