Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Security's WebAuthn relying-party support, Webauthn4JRelyingPartyOperations, does not effectively enforce its authenticator signature-counter check.
WebAuthn authenticators are expected to increment a per-credential signature counter on every use, and a relying party is expected to reject an assertion whose counter fails to increase, since a counter that repeats or regresses is a strong signal that the authenticator has been cloned.
An internal defect in how Webauthn4JRelyingPartyOperations supplies the previously stored counter to the underlying verification library means this check does not actually detect a non-incrementing counter, so this defense-in-depth control against cloned authenticators is not effective.
Preconditions:
Webauthn4JRelyingPartyOperations (Spring Security's default WebAuthn RelyingPartyOperations implementation) to authenticate users.An attacker who already possesses such a cloned authenticator can continue to authenticate as the victim without Spring Security detecting or rejecting the clone.
Spring Security:
| Fix version | Availability |
|---|---|
| 7.1.3 | OSS |
| 7.1.2.1 | Enterprise Support Only |
| 7.0.9 | OSS |
| 7.0.8.1 | Enterprise Support Only |
No further mitigation steps are necessary.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy