CVE-2024-12225
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe quarkus-security-webauthn module in Quarkus has an access control bypass where default REST endpoints for user registration and login remain accessible even when developers implement custom endpoints. This allows attackers to obtain valid authentication cookies that may correspond to existing users by simply knowing a username, enabling unauthorized authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.15.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify quarkus-security-webauthn extension is in useInspect your project build file (pom.xml, build.gradle.kts, or similar) for the quarkus-security-webauthn dependencyAffected if The dependency is present in your project and the Quarkus version is below 3.15.3.1
-
Confirm Quarkus version is vulnerableCheck the Quarkus version in your build file or the runtime environment. Compare it against the affected range: versions less than 3.15.3.1 are vulnerableAffected if Your installed Quarkus version is lower than 3.15.3.1
-
Check if custom WebAuthn REST endpoints are implementedSearch your source code for classes annotated with @Path or @RestController that handle WebAuthn registration or login operations (look for paths like /webauthn/register, /webauthn/login, or similar)Affected if Custom WebAuthn endpoint classes exist in your codebase
-
Inspect WebAuthn configuration for default endpoint settingsExamine your application.properties or application.yaml file for quarkus.webauthn configuration keys. Look for settings like enable-default-endpoints or similar flags that control whether built-in endpoints remain activeAffected if Default WebAuthn endpoints are not explicitly disabled in your configuration while custom endpoints are implemented
-
Test for accessible default endpointsSend HTTP requests to the default WebAuthn paths (such as /q/webauthn/register or /q/webauthn/login) on your running application to verify they respondAffected if The default endpoints return successful responses, indicating they remain accessible alongside your custom endpoints
You are affected if you use quarkus-security-webauthn with Quarkus version below 3.15.3.1, have implemented custom WebAuthn endpoints, and the default endpoints remain accessible without explicit configuration to disable them.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.15.3.1
When implementing custom WebAuthn REST endpoints, explicitly disable or remove the default Quarkus WebAuthn endpoints in the application configuration to prevent unauthorized access.
Quarkus 3.15.3.1 or later
- Upgrade Quarkus to version 3.15.3.1 or later
- After upgrading, verify that custom WebAuthn REST endpoints are properly implemented and the default endpoints are disabled or not accessible
- If custom endpoints are used, ensure the application properly validates user identity and does not rely solely on the WebAuthn cookie
- Test the authentication flow to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12225 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12225 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data