Home » Vulnerabilities Knowledge Base » Strong password policy is not found to be implemented
The vulnerability arises when a web application fails to implement a strong password policy during user registration, password change or reset processes.
A weak policy might allow users to:
Without proper validation, attackers can more easily exploit accounts through password guessing, brute-force attacks or credential stuffing.
The lack of a strong password policy can lead to:
To solve this problem, organizations should enforce a strong password policy for all login and password-related forms.
Ensure users create passwords that meet minimum complexity standards:
Require users to change passwords regularly, for example, every 90 days for sensitive accounts.
Prevent reuse of previously used passwords.
Implement password strength checks on the client side, providing feedback to users, and on the server side to ensure compliance with the policy, regardless of client behavior.
Make sure the strong password policy is enforced on:
Content Sniffing
Certain browsers, try to determine the content type and encoding of the response even when these properties are defined correctly...
Content Sniffing
Certain browsers, try to determine the content type and encoding of the response even when these properties are defined correctly...
Content Sniffing
Certain browsers, try to determine the content type and encoding of the response even when these properties are defined correctly...
Content Sniffing
Certain browsers, try to determine the content type and encoding of the response even when these properties are defined correctly...