On Sep 26, 2006, at 11:13 AM, [EMAIL PROTECTED] wrote:
Having done the modification proposed by Renaud, I launched :
/tools/nessus/bin/nasl -t 138.203.216.64 -T /tmp/begelsapp04.ms06-035
/tools/nessus/lib/nessus/plugins/smb_kb917159.nasl
and here is the end of the output file :
.........................................
NASL:0181> security_hole(...)
[29965](/tools/nessus/lib/nessus/plugins/smb_kb917159.nasl) NASL>
[002bdd70] -> 445
[29965]() NASL> [002bebe0] <- 445
[29965](/tools/nessus/lib/nessus/plugins/smb_kb917159.nasl) NASL> Call
security_hole(1: 445)
[29965](/tools/nessus/lib/nessus/plugins/smb_kb917159.nasl) NASL>
Return
security_hole: FAKE
NASL:0184> NetUseDel(...)
..............................................................
What is the meaning of the line "Return security_hole: FAKE" ?
Vulnerable
or not ?
security_hole() returns null which is referred to as 'fake' in Nessus
2.x. However the fact that the function itself was called indicates
that the remote host indeed is vulnerable (try to avoid using -T
without a good reason, it cluters the output).
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
