{}

{}

{}

{"bugzilla": {"description": "io.quarkus:quarkus-security-webauthn: Quarkus WebAuthn Unexpected Authentication Bypass", "id": "2330484", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2330484"}, "csaw": false, "cvss3": {"cvss3_base_score": "9.1", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "status": "draft"}, "cwe": "CWE-288", "details": ["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."], "mitigation": {"lang": "en:us", "value": "It is possible to mitigate this issue by disabling the default endpoints after creating a custom one. For example with the call for:\nimport io.vertx.ext.web.Router;\nimport jakarta.enterprise.event.Observes;\npublic class Startup {\npublic void init(@Observes Router router) {\nSystem.err.println(\"Securing WebAuthn default controller\");\nrouter.post(\"/q/webauthn/callback\").order(0).handler(rc -> rc.fail(404));\n}\n}"}, "name": "CVE-2024-12225", "package_state": [{"cpe": "cpe:/a:redhat:quarkus:3", "fix_state": "Not affected", "package_name": "io.quarkus:quarkus-security-webauthn", "product_name": "Red Hat build of Quarkus"}], "public_date": "2025-02-28T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2024-12225\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-12225"], "statement": "The Red Hat build of Quarkus does not support the quarkus-security-webauthn module.", "threat_severity": "Important"}