Products

Solutions

Resources

/

/

Default Login Credetials

Default Login Credetials

Detection of default login credentials misconfiguration for potential unauthorized access vulnerability.

Security Misconfiguration (SM)

The Default Login Credentials test is designed to identify security misconfigurations where default or commonly used login credentials are employed in an application. By modifying the request parameters, including username and password, with a predefined list of default values, the test checks if the application accepts these credentials. This misconfiguration falls under the Security Misconfiguration category with a low severity level. Utilizing default login credentials can expose the system to unauthorized access, posing a significant risk of data breaches and unauthorized actions. It is crucial to avoid default credentials for enhanced security.

The Default Login Credentials test is designed to identify security misconfigurations where default or commonly used login credentials are employed in an application. By modifying the request parameters, including username and password, with a predefined list of default values, the test checks if the application accepts these credentials. This misconfiguration falls under the Security Misconfiguration category with a low severity level. Utilizing default login credentials can expose the system to unauthorized access, posing a significant risk of data breaches and unauthorized actions. It is crucial to avoid default credentials for enhanced security.

Impact of the vulnerability

Impact of the vulnerability

Default login credentials expose the system to unauthorized access, increasing the risk of data breaches and unauthorized actions.

Default login credentials expose the system to unauthorized access, increasing the risk of data breaches and unauthorized actions.

How this template works

APIs Selection

The API selection filters in this template are used to filter the requests based on specific criteria. In this case, the filters are set to select requests with a response code between 200 and 299, and requests that have either "username" or "user" as a key in the request payload.

Execute request

The execute section of the template specifies the type of execution as "single" and defines the requests to be executed. In this case, the request is modified by replacing the "usernameKey" parameter with values from the "usernames" word list, and the "passwordKey" parameter is set to "admin".

Validation

The validation section defines the criteria for validating the response. It specifies that the response code should be between 200 and 205. This ensures that the request was successful and the response is within the expected range.

Frequently asked questions

What is the purpose of the Default Login Credentials test

What is the purpose of the Default Login Credentials test

What is the purpose of the Default Login Credentials test

How does the Default Login Credentials test work

How does the Default Login Credentials test work

How does the Default Login Credentials test work

What is the impact of using default login credentials

What is the impact of using default login credentials

What is the impact of using default login credentials

What category and severity level does the Default Login Credentials test fall under

What category and severity level does the Default Login Credentials test fall under

What category and severity level does the Default Login Credentials test fall under

Are there any specific word lists used for the username parameter in this test

Are there any specific word lists used for the username parameter in this test

Are there any specific word lists used for the username parameter in this test

Are there any references or resources available for further information on security misconfigurations

Are there any references or resources available for further information on security misconfigurations

Are there any references or resources available for further information on security misconfigurations

Loved by security teams!

Loved by security teams!

Product Hunt Badge

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "

Rippling Company logo

Security team,

Rippling

Suggest API security tests

Suggest API security tests

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.