Default Credentials

Many web applications are set up with default credentials to allow access after installation. However, these credentials need to be changed after the initial setup of the web application; otherwise, they provide an easy way for attackers to obtain authenticated access. As such, Testing for Default Credentials is an essential part of authentication testing in OWASP's Web Application Security Testing Guide. According to OWASP, common default credentials include admin and password.

Testing Default Credentials

Many platforms provide lists of default credentials for a wide variety of web applications. An example of this is the web database maintained by CIRT.net. For instance, if we identified a Cisco device during a penetration test, we can search the database for default credentials for Cisco devices:

CIRT.net Default Password DB page showing search bar and list of default passwords. Example: Cisco with user ID and password details. Navigation menu and subscription form on the left.

Further resources include SecLists Default Credentials as well as the SCADA GitHub repository, which contains a list of default passwords for a variety of different vendors.

A targeted internet search is a different way of obtaining default credentials for a web application. Let us assume we stumble across a BookStack web application during an engagement:

BookStack Demo login page with fields for email and password. Options for "Remember Me" and password recovery. Navigation includes Shelves, Books, and Log in.

We can try to search for default credentials by searching something like bookstack default credentials:

Google search results for "bookstack default credentials" showing default admin login: admin@admin.coml with password "password". Suggests changing details after first login.

As we can see, the results contain the installation instructions for BookStack, which state that the default admin credentials are admin@admin.com:password.