160 likes | 275 Views
This comprehensive checklist provides a systematic approach to identifying, assessing, and mitigating vulnerabilities in web applications. It covers critical aspects such as parameter validation, credential management, session management, authentication flaws, input validation vulnerabilities like SQL injection, and misconfigurations. By implementing the recommendations outlined on URL encoding, error message handling, and secure password storage, developers can significantly enhance the security posture of their applications. Regular audits and updates based on this checklist can help maintain robust defenses against web-based threats.
E N D
Parameter Checklist • URL request • URL encoding • Query string • Header • Cookie • Form field • Hidden field • Client side validation • ‘Tainted’ parameters • Min/Max lengths • Concatenate commands
Credential Management • Password storage • Password change • User Update section • Password strength • Lockout policy • Login attempts allowed
Session Management • Token protection • Session Duration • Idle time Duration • Guess Session ID format • Transfer in URL or BODY? • Is Session Id linked to the IP address? • Change Referrer tag
Backend Authentication • Trust relationships • Encryption • Plaintext password in HTML • Password in configuration file.
XSS • Which type – stored or reflected • Check for 404/500 error pages for • return information. • Input validation
MisConfiguration • Nikto results • Nessus results • Patch level • Directory listing • Directory permission • Error messages • Default username/pass • SSL cert. Configuration • Debug or configuration Files • Check for latest vulnerabilities
Unwanted • Backup files • Defaults files • Services • Remote admin. Access
Flaws in access control? • Check for path transversal. • Client side Caching • Check header • Check metatag • Determine file permissions
SQL injection • Mirror website and search for all input parameters • Gain database related information • Error Messages • Privileges given to the webserver or database
OS calls • Using any interpreter? • OS service calls (e.g. Sendmail) • Mirror and search code for all calls to external sources. • Privileges given to other services and webserver.
Complete check of information returned in error messages. Guess • application logic through errors codes and messages. • Deconstruction of binary codes (if any) • Is critical data secured and encrypted?
Examine • Token • Cookie • SSID • Serialized Objects
Access points • Regular users • Admin access • Any other?
Ability to brute force at the discovered access points. • Ability to bypass auth. with spoofed tokens • Ability to conduct replay attack. • Forced browsing, does application keep a check by tracking request from each user.