Testing for authentication
Default or guessable user accounts
The source for this problem is often inexperienced IT personnel, unaware of the importance of changing default passwords on installed infrastructure components, programmers, leaving backdoors so they can easily access and test the application, later forgetting to remove them, application administrators and users that chose an easy username and password for themselves, and application with built in, non-removable default accounts with a preset username and password. Another problem is blank passwords, which are simply a result of security unawareness and willingness to simplify things.
Note - before approaching the test, it is important to understand whether the environment you are testing is a production environment. Modifying passwords or locking out users on a production environment can lead to undesired consequences.
In blackbox testing we know nothing about the application, its underlying infrastructure, and any username and/or password policies. Often this is not the case and some information about the application is provided – simply skip the steps that refer to obtaining information you already have.
When testing a known application interface, such as a Cisco router web interface, or Weblogic admin access, check the known usernames and passwords for these devices. This can be done either by Google, or using one of the references in the Further Reading section.
When facing a homegrown application, to which we do not have a list of default and common user accounts, we need to test it manually, following these guidelines:
- Try the following usernames - "admin", "administrator", "root", "system", or "super". These are popular among system administrators and are often used. Additionally you could try "qa", "test", "test1", "testing", and similar names. Attempt any combination of the above in both the username and the password fields. If the application is vulnerable to username enumeration, and you successfully managed to identify any of the above usernames, attempt passwords in a similar manner.
- Application administrative users are often named after the application. This means if you are testing an application named "Obscurity", try using obscurity/obscurity as the username and password.
- When performing a test for a customer, attempt using names of contacts you have received as usernames.
- Attempt using all the above usernames with blank passwords.
Suggested Tools - <TBD>
The steps described next rely on an entirely White Box approach. If only some of the information is available to you, refer to blackbox testing to fill the gaps.
- Talk to the IT personnel to determine which passwords they use for administrative access. Check whether these usernames and passwords are complex, difficult to guess, and not related to the application name, person name, or administrative names ("system"). Note blank passwords.
- Check in the user database for default names, application names, and easily guessed names as described in the Black Box testing section. Check for empty password fields.
- Examine the code for hardcoded usernames and passwords.
Control for automated attacks? - <TBD>
(ie. does the authentication mechanism block remote systems that try a brute force attack against a simple user/password form?
[ ] [Completed]
[ ] [Completed]
Expiration at logoff
[ ] [Completed]