# Weak Password Policy A weak password policy increases the probability of an attacker having success using brute force and dictionary attacks against user accounts. An attacker who can determine user passwords can take over a user's account and potentially access sensitive data in the application. There are two ways in which this can be checked ## First Way * Check if you can use Password same as that of Email Address * Check if you can use Username same as that of Email Address * Try above mentioned when Resetting Password , Creating Account , Changing Password from Account Settings ## Second Way * Check if you can use Password some Weak Passwords such as 123456, 111111 , abcabc , qwerty123 * Try above mentioned when Resetting Password , Creating Account , Changing Password from Account Settings * Applications usually have Restrictions on Password while Creating Account, Make sure you check for both the cases when Resetting Password ## References * [All About Weak Password Policy](http://applicationsecurity.io/appsec-findings-database/weak-password-policy/) * [OWASP Guide for Weak Passwords](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/04-Authentication_Testing/07-Testing_for_Weak_Password_Policy) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kathan19.gitbook.io/howtohunt/weak-password-policy/weak_password_policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.