Skip to content

WebAuthn4J Spring Security Improper signature counter value handling

Moderate severity GitHub Reviewed Published Oct 16, 2023 in webauthn4j/webauthn4j-spring-security • Updated Nov 7, 2023

Package

maven com.webauthn4j:webauthn4j-spring-security-core (Maven)

Affected versions

< 0.9.1.RELEASE

Patched versions

0.9.1.RELEASE

Description

Improper signature counter value handling

Impact

A flaw was found in webauthn4j-spring-security-core. When an authneticator returns an incremented signature counter value during authentication, webauthn4j-spring-security-core does not properly persist the value, which means cloned authenticator detection does not work.
An attacker who cloned valid authenticator in some way can use the cloned authenticator without being detected.

Patches

Please upgrade to com.webauthn4j:webauthn4j-spring-security-core:0.9.1.RELEASE

References

For more details about WebAuthn signature counters, see WebAuthn specification 6.1.1. Signature Counter Considerations.

Reporter

This issue was discovered by Michael Budnick (@mbudnick)

References

@ynojima ynojima published to webauthn4j/webauthn4j-spring-security Oct 16, 2023
Published by the National Vulnerability Database Oct 16, 2023
Published to the GitHub Advisory Database Oct 17, 2023
Reviewed Oct 17, 2023
Last updated Nov 7, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.079%
(36th percentile)

Weaknesses

CVE ID

CVE-2023-45669

GHSA ID

GHSA-v9hx-v6vf-g36j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.