Products

Solutions

Resources

/

/

Sensitive Configuration Files Listing

Sensitive Configuration Files Listing

Directory listing of sensitive files.

Security Misconfiguration (SM)

Business Logic

"Sensitive Configuration Files Listing refers to the vulnerability where the misconfiguration allows the listing of sensitive configuration files located in the "config" directory. This exposure can disclose critical information like database credentials and API keys, posing a significant risk to the application's security. Promptly addressing this vulnerability is essential to prevent unauthorized access and protect sensitive data from exploitation."

"Sensitive Configuration Files Listing refers to the vulnerability where the misconfiguration allows the listing of sensitive configuration files located in the "config" directory. This exposure can disclose critical information like database credentials and API keys, posing a significant risk to the application's security. Promptly addressing this vulnerability is essential to prevent unauthorized access and protect sensitive data from exploitation."

Impact of the vulnerability

Impact of the vulnerability

Listing sensitive configuration files exposes critical information, such as database credentials and API keys, enabling targeted attacks and unauthorized access.

Listing sensitive configuration files exposes critical information, such as database credentials and API keys, enabling targeted attacks and unauthorized access.

How this template works

APIs Selection

The API selection filters in this template specify the criteria for selecting the APIs to be tested. In this case, the filters include the response code filter, which selects APIs with a response code greater than or equal to 200 and less than 300, and the URL filter, which extracts the URL from the response and assigns it to the variable "urlVar".

Execute request

The execute section of the template defines the type of request to be executed. In this case, it is a single request. The request is modified using the "modify_url" action, where the URL variable "urlVar" is appended with "/config/". This modified URL is used to send the request.

Validation

The validation section specifies the conditions that the response should meet to be considered valid. In this template, the response code is validated to be equal to 200, indicating a successful request. Additionally, the response payload is checked to ensure it contains both "Index of /configs" and "Parent Directory" strings. If these conditions are met, the validation is successful.

Frequently asked questions

What is the purpose of the "CONFIGURATION_LISTING" array in this test

What is the purpose of the "CONFIGURATION_LISTING" array in this test

What is the purpose of the "CONFIGURATION_LISTING" array in this test

How does the vulnerability described in the "CONFIGURATION_LISTING" array pose a risk to the application's security

How does the vulnerability described in the "CONFIGURATION_LISTING" array pose a risk to the application's security

How does the vulnerability described in the "CONFIGURATION_LISTING" array pose a risk to the application's security

What is the severity level assigned to the vulnerability described in the "CONFIGURATION_LISTING" array

What is the severity level assigned to the vulnerability described in the "CONFIGURATION_LISTING" array

What is the severity level assigned to the vulnerability described in the "CONFIGURATION_LISTING" array

What is the category and subcategory of the vulnerability described in the "CONFIGURATION_LISTING" array

What is the category and subcategory of the vulnerability described in the "CONFIGURATION_LISTING" array

What is the category and subcategory of the vulnerability described in the "CONFIGURATION_LISTING" array

What are the API selection filters defined in this test

What are the API selection filters defined in this test

What are the API selection filters defined in this test

How is the vulnerability validated in this test

How is the vulnerability validated in this test

How is the vulnerability validated in this test

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.