Laravel - Sensitive Information Disclosure

A Laravel .env file was discovered, which stores sensitive information like database credentials and tokens. It should not be publicly accessible.

Security Misconfiguration (SM)

Impact of the vulnerability

Publicly exposing the Laravel .env file exposes sensitive information like database credentials and API keys, leading to potential unauthorized access, data breaches, and compromise of the application's security.

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 range (between 200 and 299) and the extraction of the "urlVar" variable from the URL.

Execute request

The execute section of the template defines the type of request to be executed and the modifications to be made to the URL. In this case, a single request is made, and the URL is modified using the "urlPaths" word list, which contains various paths related to the Laravel .env file.

Validation

The validation section specifies the conditions that the response should meet to be considered valid. In this template, the response code should be equal to 200, and the response payload should contain at least one of the specified sensitive information keywords related to the Laravel .env file.

Frequently asked questions

What is the purpose of the Laravel .env file

Why is it important to secure the .env file

How can the Laravel .env file be protected

What are the potential risks of exposing the Laravel .env file

Are there any specific file naming conventions for the Laravel .env file

What are some recommended resources for securing the Laravel .env file

Loved by security teams!

"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."

Security team,

Loom

Security team,

Loom

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. "

Security team,

Rippling

Security team,

Rippling

Security team,

Rippling

Explore other tests

eSMTP - Config Discovery

Nginx - Git Configuration Exposure

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

circleci config.yml exposure

Learn more:

Content

4 min read

Introducing AktoGPT to secure APIs

Content

10 min read

What's changed in OWASP API Security Top 10 2023 Release Candidate from 2019?

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.