CVE-2024-47056: Mautic does not shield .env files from web traffic
Summary This advisory addresses a security vulnerability in Mautic where sensitive .env configuration files may be directly accessible via a web browser. This exposure could lead to the disclosure of sensitive information, including database credentials, API keys, and other critical system configurations.
Sensitive Information Disclosure via .env File Exposure: The .env file, which typically contains environment variables and sensitive application configurations, is directly accessible via a web browser due to missing web server configurations that restrict access to such files. This allows an unauthenticated attacker to view the contents of this file by simply navigating to its URL.
Mitigation Update Mautic to the latest Mautic version. By default, Mautic does not use .env files for production data.
For Apache users: Ensure your web server is configured to respect .htaccess files.
For Nginx users: As Nginx does not inherently support .htaccess files, you must manually add a configuration block to your Nginx server configuration to deny access to .env files. Add the following to your Nginx configuration for the Mautic site:
nginx location ~ /\.env { deny all; }
After modifying your Nginx configuration, remember to reload or restart your Nginx service for the changes to take effect.
Other sources
SummaryThis advisory addresses a security vulnerability in Mautic where sensitive .env configuration files may be directly accessible via a web browser. This exposure could lead to the disclosure of sensitive information, including database credentials, API keys, and other critical system configurations.
Sensitive Information Disclosure via .env File Exposure: The .env file, which typically contains environment variables and sensitive application configurations, is directly accessible via a web browser due to missing web server configurations that restrict access to such files. This allows an unauthenticated attacker to view the contents of this file by simply navigating to its URL.
MitigationUpdate Mautic to the latest Mautic version.
By default, Mautic does not use .env files for production data.
For Apache users: Ensure your web server is configured to respect .htaccess files.
For Nginx users: As Nginx does not inherently support .htaccess files, you must manually add a configuration block to your Nginx server configuration to deny access to .env files. Add the following to your Nginx configuration for the Mautic site:
location ~ /\.env { deny all; }
After modifying your Nginx configuration, remember to reload or restart your Nginx service for the changes to take effect.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47056?
CVE-2024-47056 has a high severity rating due to the risk of exposing sensitive information through accessible .env files.
How do I fix CVE-2024-47056?
To fix CVE-2024-47056, ensure that your .env files are not publicly accessible and implement proper server configurations.
What information could be exposed by CVE-2024-47056?
CVE-2024-47056 may expose sensitive information such as database credentials, API keys, and other critical configuration data.
Which software is affected by CVE-2024-47056?
CVE-2024-47056 affects Mautic, particularly its configuration file access settings.
Is there a workaround for CVE-2024-47056?
A workaround for CVE-2024-47056 includes securing your web server to restrict access to the .env files.