Cloned authenticator evasion via discarded counter updates
Published Oct 16, 2023 · Updated Sep 13, 2024
Improper authentication in WebAuthn4J Spring Security before 0.9.1.RELEASE allows attackers with a cloned authenticator to evade detection. WebAuthnAuthenticationProvider.doAuthenticate passes a new AuthenticatorImpl to verification, so the returned counter update never reaches the persisted WebAuthnAuthenticator object. Exploitation requires possession of a cloned valid authenticator; authentication can then proceed without the relying party detecting counter reuse.
Summary
What happened
Improper authentication in WebAuthn4J Spring Security before 0.9.1.RELEASE allows attackers with a cloned authenticator to evade detection. WebAuthnAuthenticationProvider.doAuthenticate passes a new AuthenticatorImpl to verification, so the returned counter update never reaches the persisted WebAuthnAuthenticator object. Exploitation requires possession of a cloned valid authenticator; authentication can then proceed without the relying party detecting counter reuse.
The record
- CVE
- CVE-2023-45669
- Published
- Oct 16, 2023
- Updated
- Sep 13, 2024
- Vendor
- WebAuthn4J
- Product
- WebAuthn4J Spring Security
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2023CVE publishedPublication date reported by the CVE source.
- Sep 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.9.1.RELEASE
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo