fkie_cve-2024-47056
Vulnerability from fkie_nvd
Published
2025-05-28 17:15
Modified
2025-05-29 14:29
Severity ?
5.1 (Medium) - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Summary
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.
References
security@mautic.orghttps://github.com/mautic/mautic/security/advisories/GHSA-h2wg-v8wg-jhxh
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "SummaryThis advisory addresses a security vulnerability in Mautic where sensitive .env\u00a0configuration 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.\n\nSensitive Information Disclosure via .env\u00a0File Exposure: The .env\u00a0file, 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.\n\nMitigationUpdate Mautic to the latest Mautic version.\n\nBy default, Mautic does not use .env\u00a0files for production data.\n\nFor Apache users:\u00a0Ensure your web server is configured to respect .htaccess\u00a0files.\n\nFor Nginx users:\u00a0As Nginx does not inherently support .htaccess\u00a0files, you must manually add a configuration block to your Nginx server configuration to deny access to .env\u00a0files. Add the following to your Nginx configuration for the Mautic site:\n\nlocation ~ /\\.env {\n    deny all;\n}\n\n\n\n\n\nAfter modifying your Nginx configuration, remember to reload or restart your Nginx service for the changes to take effect."
    },
    {
      "lang": "es",
      "value": "Resumen: Este aviso aborda una vulnerabilidad de seguridad en Mautic que permite acceder directamente a archivos de configuraci\u00f3n .env confidenciales a trav\u00e9s de un navegador web. Esta exposici\u00f3n podr\u00eda provocar la divulgaci\u00f3n de informaci\u00f3n confidencial, como credenciales de bases de datos, claves de API y otras configuraciones cr\u00edticas del sistema. Divulgaci\u00f3n de informaci\u00f3n confidencial mediante la exposici\u00f3n de archivos .env: El archivo .env, que suele contener variables de entorno y configuraciones confidenciales de aplicaciones, es accesible directamente a trav\u00e9s de un navegador web debido a la falta de configuraciones del servidor web que restringen el acceso a dichos archivos. Esto permite que un atacante no autenticado vea el contenido de este archivo simplemente accediendo a su URL. Mitigaci\u00f3n: Actualice Mautic a la \u00faltima versi\u00f3n. De forma predeterminada, Mautic no utiliza archivos .env para datos de producci\u00f3n. Para usuarios de Apache: Aseg\u00farese de que su servidor web est\u00e9 configurado para respetar los archivos .htaccess. Para usuarios de Nginx: Dado que Nginx no admite archivos .htaccess de forma inherente, debe agregar manualmente un bloque de configuraci\u00f3n a la configuraci\u00f3n de su servidor Nginx para denegar el acceso a los archivos .env. Agregue lo siguiente a su configuraci\u00f3n de Nginx para el sitio de Mautic: location ~ /\\.env { deny all; } Despu\u00e9s de modificar su configuraci\u00f3n de Nginx, recuerde volver a cargar o reiniciar su servicio Nginx para que los cambios surtan efecto."
    }
  ],
  "id": "CVE-2024-47056",
  "lastModified": "2025-05-29T14:29:50.247",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "LOW",
          "baseScore": 5.1,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 2.5,
        "impactScore": 2.5,
        "source": "security@mautic.org",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-05-28T17:15:23.547",
  "references": [
    {
      "source": "security@mautic.org",
      "url": "https://github.com/mautic/mautic/security/advisories/GHSA-h2wg-v8wg-jhxh"
    }
  ],
  "sourceIdentifier": "security@mautic.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-312"
        }
      ],
      "source": "security@mautic.org",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.