CVE-2024-36119

{"id": "CVE-2024-36119", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 1.8, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 0.3}]}, "published": "2024-05-30T21:15:09.460", "references": [{"url": "https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5", "source": "security-advisories@github.com"}, {"url": "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository", "source": "security-advisories@github.com"}, {"url": "https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e", "source": "security-advisories@github.com"}, {"url": "https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-312"}]}], "descriptions": [{"lang": "en", "value": "Statamic is a, Laravel + Git powered CMS designed for building websites. In affected versions users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file. This only affects sites matching **all** of the following conditions: 1. Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week), 2. Using the `user:register_form` tag. 3. Using file-based user accounts. (Does not affect users stored in a database.), 4. Has users that have registered during that time period. (Existing users are not affected.). Additionally passwords are only visible to users that have access to read user yaml files, typically developers of the application itself. This issue has been patched in version 5.6.2, however any users registered during that time period and using the affected version range will still have the the `password_confirmation` value in their yaml files. We recommend that affected users have their password reset. System administrators are advised to upgrade their deployments. There are no known workarounds for this vulnerability. Anyone who commits their files to a public git repo, may consider clearing the sensitive data from the git history as it is likely that passwords were uploaded."}, {"lang": "es", "value": "Statamic es un CMS con tecnolog\u00eda Laravel + Git manipulado para crear sitios web. En las versiones afectadas, los usuarios que se registren a trav\u00e9s de la etiqueta `user:register_form` tendr\u00e1n la confirmaci\u00f3n de su contrase\u00f1a almacenada en texto sin formato en su archivo de usuario. Esto solo afecta a los sitios que cumplen **todas** las siguientes condiciones: 1. Ejecutar versiones de Statamic entre 5.3.0 y 5.6.1. (Este rango de versiones representa solo una semana calendario), 2. Usando la etiqueta `user:register_form`. 3. Usar cuentas de usuario basadas en archivos. (No afecta a los usuarios almacenados en una base de datos). 4. Tiene usuarios que se han registrado durante ese per\u00edodo de tiempo. (Los usuarios existentes no se ven afectados). Adem\u00e1s, las contrase\u00f1as solo son visibles para los usuarios que tienen acceso para leer archivos yaml de usuario, generalmente desarrolladores de la propia aplicaci\u00f3n. Este problema se solucion\u00f3 en la versi\u00f3n 5.6.2; sin embargo, cualquier usuario registrado durante ese per\u00edodo de tiempo y que utilice el rango de versiones afectado a\u00fan tendr\u00e1 el valor `password_confirmation` en sus archivos yaml. Recomendamos que los usuarios afectados restablezcan su contrase\u00f1a. Se recomienda a los administradores del sistema que actualicen sus implementaciones. No se conocen workarounds para esta vulnerabilidad. Cualquiera que env\u00ede sus archivos a un repositorio p\u00fablico de git puede considerar borrar los datos confidenciales del historial de git, ya que es probable que se hayan cargado contrase\u00f1as."}], "lastModified": "2024-05-31T13:01:46.727", "sourceIdentifier": "security-advisories@github.com"}