This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Joomla Vulnerability Scanner Limitations"
From OWASP
D0ubl3 h3lix (talk | contribs) (→Limitations) |
D0ubl3 h3lix (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Limitations on Current Release== | ==Limitations on Current Release== | ||
| − | * The vulnerability database still lacks of unknown exploit checks. If the exploit check is not available, the scanner cannot verify the vulnerability | + | * The vulnerability database still lacks of unknown exploit checks. If the exploit check is not available, the scanner verify based on deduced version. |
| + | If deduced version is not available, it then cannot verify the vulnerability | ||
* The Scanner lacks IDS evasion bypass | * The Scanner lacks IDS evasion bypass | ||
* The Scanner lacks sophisticated fuzzing | * The Scanner lacks sophisticated fuzzing | ||
Revision as of 17:58, 15 July 2009
Limitations on Current Release
- The vulnerability database still lacks of unknown exploit checks. If the exploit check is not available, the scanner verify based on deduced version.
If deduced version is not available, it then cannot verify the vulnerability
- The Scanner lacks IDS evasion bypass
- The Scanner lacks sophisticated fuzzing
- The Scanner is not a full fledged SQL Injection tool
