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 "Testing for Captcha (OWASP-AT-012)"

From OWASP
Jump to: navigation, search
(Security Note)
(WARNING: CAPTCHA is considered to be an ineffective security mechanism - most current CAPTCHAs in these days can be cracked in a fully automated way!)
Line 2: Line 2:
  
  
=== WARNING: CAPTCHA is considered to be an ineffective security mechanism - most current CAPTCHAs in these days can be cracked in a fully automated way! ===
+
=== WARNING: CAPTCHA is considered to be an ineffective security mechanism - most current CAPTCHA images in these days can be cracked in a fully automated way! ===
  
 
== Brief Summary ==
 
== Brief Summary ==

Revision as of 23:51, 17 November 2013

This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents Back to the OWASP Testing Guide Project: https://www.owasp.org/index.php/OWASP_Testing_Project


WARNING: CAPTCHA is considered to be an ineffective security mechanism - most current CAPTCHA images in these days can be cracked in a fully automated way!

Brief Summary


CAPTCHA ("Completely Automated Public Turing test to tell Computers and Humans Apart") is a type of challenge-response test used by many web applications to ensure that the response is not generated by a computer.

Security Note:

Description of the Issue


...here: Short Description of the Issue: Topic and Explanation

Black Box testing and example

Testing for Topic X vulnerabilities:
...
Result Expected:
...

References

Whitepapers
...
Tools
...