There's a new Open Source Vulnerability database at http://www.osvdb.org/ which just opened up. The goal is to have a more responsive/faster turn around database vs. the others (e.g. CVE). No clue whether the concept will work or not.
Anyway, there are two 'ntop' items already listed, but as they have not been 'moderated', they're not visible yet. 1496 claims ntop's web server can be used via .. to view arbitrary files. This is just the old CVE-2000-0705 problem. Neither 2.2c nor 3.0 are vulnerable. (Nor any version since 1.3) 2.2c logs the attempt via URLsecurity: **ERROR** URL security(3): ERROR: Found .. in URL...rejecting request 3.0 logs it and also returns a 408 message to the user. 1513 claims that ntop is vulnerable to buffer overflows via the web server. No specific version nor command is given. This used to be true - but the only *known* case was fixed in 2.1. We've undertaken a process to remove all possible insecure functions (sprintf, strcat, etc.). With ntop 3.0 - as far as we know - every former sprintf() which uses user provided data is now an sprintf() and protected. There has already been one patch to the development tree to convert the majority of the (few) remaining sprintf()'s to snprintf()'s, just for safety's sake. As always, if you have concerns, ask on the mailing list. If you find a problem, contact Luca or myself off-list - and we WILL take care of it. -----Burton _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
