Signature Detail
Short Name |
HTTP:EXPLOIT:BRUTE-SEARCH |
|---|---|
Severity |
High |
Recommended |
No |
Category |
HTTP |
Keywords |
http brute search |
Release Date |
2004/01/27 |
Update Number |
1213 |
Supported Platforms |
di-5.3+, idp-4.0+, isg-3.0+, j-series-9.5+, mx-9.4+, srx-9.2+, srx-branch-9.4+, vsrx-12.1+ |
HTTP: Brute Search Attempt
This protocol anomaly is multiple 301 (Moved Permanently), 403 (Forbidden), 404 (Not Found) and 405 (Method Not Allowed) errors between a unique pair of hosts within a short period of time. This could indicate that a search robot or a script is methodically searching a Web site for vulnerable directories or CGI scripts. The default maximum number of 301/403/404/405 errors is 16; you can change this setting in the Sensor Settings Rulebase>Protocol Thresholds and Configuration>HTTP>Maximum Number of 301/403/404/405 Errors Per Minute.
Extended Description
If a website logs a great number of HTTP response codes such as 301 (Moved Permanently), 403 (Forbidden), 404 (Not Found) and 405 (Method Not Allowed), it could indicate a search robot or a script is methodically searching a website for vulnerability.
References
- BugTraq: 42695
- CVE: CVE-2010-3146
- URL: http://en.wikipedia.org/wiki/Brute_force_attack