Active Directory
Web services
Systems & services
🛠️ Physical
🛠️ binary exploitation
🛠️ Logging in
Theory
link default passwords
Authentication issues are important to take into consideration. A login page can be the beginning of serious issues regarding accounts takeover.
or bruteforce
Practice
or authentication bypass
Brute-force
Brute-forcing can have 2 interesting purposes during a pentest engagement:
- 1.Verifying that the web application implements security measures against brute-forcing.
- 2.Taking over an account by guessing its credentials.
One has to check whether a defense mechanism is used (account locking, blocking IP, CAPTCHA, etc.)
Account locking can lead to a denial of service and allow user enumeration. Check the OWASP recommendation on how it should be implemented.
User enumeration
User enumeration can be made possible depending on the:
- Status code (is the status code retrieved, always the same?)
- Error messages (does the error messages give a hint on whether the account exists?)
- Response time (is the response time always the same?)
JSON Web Tokens (JWS) / OAuth 2.0
SQL injection
1
sqlmap -r $REQUEST_FILE -p $LOGIN_PARAM,$PWD_PARAM
Copied!
Use the
--level and --delay options in pentest engagements to avoid issues (aggressive payloads and denial of service)🛠️ NoSQL injection
🛠️ LDAP injection
Encrypted requests
Some web applications don't use TLS to encrypt login requests, this can lead to account takeover via a Man-in-the-Middle attack.
References
Vulnerabilities in password-based login | Web Security Academy
WebSecAcademy
How to secure your authentication mechanisms | Web Security Academy
WebSecAcademy
JSON Web Token for Java - OWASP Cheat Sheet Series
Authentication - OWASP Cheat Sheet Series
What Is Broken Authentication?
Auth0 - Blog
A2:2017-Broken Authentication | OWASP
Login Bypass
HackTricks
Last modified 3mo ago