Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Parameter fuzzing and forced browsing |
|---|---|
| Date: | Thu, 10 Aug 2006 09:55:22 +1000 |
On 9 Aug 2006 14:26:59 -0000, indianwhitehathacker@yahoo.com <indianwhitehathacker@yahoo.com> wrote:
I was going through the OWASP Top Ten Guide and I came across these terms:-
1. Parameter fuzzing
2. Forced browsing
What are these? Is forced browsing something like an attempt to access a resource that I am not supposed to access by putting the direct link with the necessary parameter values in a hope that may be in that page the authentication is broken?
Also, I read about fuzzers. Can someone throw light on what are fuzzers?
come on now, searching can give you all the answers...
but fuzzing is the process if sending in random data and seeing if the app crashes. the data be close to real data (a little fuzzy) or not close to real data at all (very fuzz).
'forced browsing' would, i guess, refer to the act of making the victims browser visit a page they didn't intend. done via some xss or even header injection into a badly santised 'redirect'.
but i'd think the OWASP Guide itself may document these things. maybe not. i'm sure the appropriate person will comment at the suggestion it doesn't, though :)
-- mic
------------------------------------------------------------------------- Sponsored by: Watchfire
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Ruby On Rails 1.1.5 Released to Address Critical Vulnerability, bugtraq |
|---|---|
| Next by Date: | Re: Environment for testing WebApp Security Scanners, mikeiscool |
| Previous by Thread: | Parameter fuzzing and forced browsing, indianwhitehathacker |
| Next by Thread: | Re: Parameter fuzzing and forced browsing, Ryan Barnett |
| Indexes: | [Date] [Thread] [Top] [All Lists] |