How this template works
APIs Selection
The API selection filters in this template specify the criteria for selecting the URLs to be tested. In this case, the filters include the response code range (between 200 and 299) and the extraction of the URL from the response using the "urlVar" variable.
Execute request
The execute section defines the type of request to be made and the specific request(s) to be executed. In this template, a single request is made to modify the URL by appending "/.git/config" to it. The "${urlVar}" variable is used to dynamically insert the extracted URL from the API selection filters.
Validation
The validation section specifies the conditions that the response should meet to be considered valid. In this template, the response code is expected to be 200, and the response payload should contain the string "[core]". Additionally, the response payload should not contain any of the listed HTML tags, indicating that the Git config file is not exposed.
Frequently asked questions
"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. "
Security team,
Rippling
Explore other tests
eSMTP - Config Discovery
Nginx - Git Configuration Exposure
Laravel - Sensitive Information Disclosure
Docker Container - Misconfiguration Exposure
Msmtp - Config Exposure
Parameters.yml - File Discovery
Mongo Express - Unauthenticated Access
Apache Airflow Configuration Exposure
Dockerrun AWS Configuration Exposure
Apache Config file disclosure
Appspec Yml Disclosure
CGI script environment variable
