On Sun, 2 Feb 2003, Melle, Jens wrote: > If I scan a wide range of addresses and I find a lot of vulnerabilities, > it would be really usefull, to see (in addition) the vulnerabilities - > sorted by type of vulnerability .
Yep, I'd like something like that too. Unfortunately, determining whether two entries in a Nessus report correspond to the same vuln is rather tricky. You cannot use the text because it often contains target specific data like versions or names (and this is a good thing) and you cannot use plugin id either because one plugin can generate multiple different reports (and this is unavoidable because one test may discover different things, and it would be silly to duplicate code (and runtime effort) in such a case). And CVEs are useless as well as some vulns have no CVE and a script reporting multiple CVEs cannot tell what particular CVE should be used for a particular report (well, ok, something nasty like calling set_cve_id before security_*() might work). I think this problem can be solved by making the plugin summary really useful: the summary would become the "vulnerability id", and it would be possible to set a specific summery (and CVE etc) for a particular invocation of security_hole() et al. --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation."
