CVE-2024-12225

{"id": "CVE-2024-12225", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "published": "2025-05-06T20:15:25.747", "references": [{"url": "https://access.redhat.com/security/cve/CVE-2024-12225", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2330484", "source": "secalert@redhat.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-288"}]}], "descriptions": [{"lang": "en", "value": "A vulnerability was found in Quarkus in the quarkus-security-webauthn module. The Quarkus WebAuthn module publishes default REST endpoints for registering and logging users in while allowing developers to provide custom REST endpoints. When developers provide custom REST endpoints, the default endpoints remain accessible, potentially allowing attackers to obtain a login cookie that has no corresponding user in the Quarkus application or, depending on how the application is written, could correspond to an existing user that has no relation with the current attacker, allowing anyone to log in as an existing user by just knowing that user's user name."}, {"lang": "es", "value": "Se detect\u00f3 una vulnerabilidad en Quarkus en el m\u00f3dulo quarkus-security-webauthn. El m\u00f3dulo Quarkus WebAuthn publica endpoints REST predeterminados para el registro e inicio de sesi\u00f3n de los usuarios, a la vez que permite a los desarrolladores proporcionar endpoints REST personalizados. Cuando los desarrolladores proporcionan endpoints REST personalizados, los endpoints predeterminados permanecen accesibles, lo que podr\u00eda permitir a los atacantes obtener una cookie de inicio de sesi\u00f3n que no tiene un usuario correspondiente en la aplicaci\u00f3n Quarkus o, dependiendo de c\u00f3mo est\u00e9 escrita la aplicaci\u00f3n, podr\u00eda corresponder a un usuario existente sin relaci\u00f3n con el atacante actual, lo que permite a cualquiera iniciar sesi\u00f3n como un usuario existente con solo conocer su nombre de usuario."}], "lastModified": "2025-05-07T14:13:20.483", "sourceIdentifier": "secalert@redhat.com"}