{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-12225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-12225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-12225 is a critical authentication bypass vulnerability in Red Hat build of Quarkus, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-12225 and fix it if it is affected.\n\nWhat it is: CVE-2024-12225 is a critical authentication bypass vulnerability in Red Hat build of Quarkus, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-12225 in the wild and no public exploit code.\n\nAffected product: Red Hat build of Quarkus. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-12225/ (Markdown: https://insights.sbomify.com/CVE-2024-12225/index.md)","id":"CVE-2024-12225","markdown":"https://insights.sbomify.com/CVE-2024-12225/index.md","name":"CVE-2024-12225","record":{"aliases":["GHSA-jw23-2xqx-f9f7"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Quarkus WebAuthn module","requires_auth":"none","summary":"Attackers can bypass authentication and log in as existing users by accessing default WebAuthn endpoints when custom endpoints are configured.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quarkus","vendor":"quarkus"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass","id":"CVE-2024-12225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Kubernetes Worker or Kubernetes Agent","id":"CVE-2024-12226"},"packages":[],"prev":{"headline":"idna accepts Punycode labels that do not produce any non-ASCII when decoded","id":"CVE-2024-12224"},"products":["Red Hat build of Quarkus"],"published":"2025-05-06","related":[{"cvss_score":9.8,"headline":"Code injection in quarkus dev ui config editor","id":"CVE-2022-4116","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":9.8,"headline":"Quarkus does not terminate HTTP requests header context","id":"CVE-2022-2466","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":8.8,"headline":"Quarkus authorization bypass via semicolon path normalization inconsistency","id":"CVE-2026-39852","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Privilege escalation in quarkus","id":"CVE-2022-0981","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":8.6,"headline":"Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.","id":"CVE-2023-6267","kev_date_added":null,"published":"2024-01-25"},{"cvss_score":8.1,"headline":"Quarkus: http security policy bypass","id":"CVE-2023-4853","kev_date_added":null,"published":"2023-09-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-20","vendors":["Red Hat"]},"summary":"Attackers can bypass authentication and log in as existing users by accessing default WebAuthn endpoints when custom endpoints are configured.","url":"https://insights.sbomify.com/CVE-2024-12225/"}