# CVE-2023-45669: Improper signature counter value handling in webauthn4j-spring-security

> Attackers can use cloned authenticators without detection due to improper signature counter persistence in webauthn4j-spring-security.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2023
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-v9hx-v6vf-g36j

## What is CVE-2023-45669?

CVE-2023-45669 is a medium-severity vulnerability in webauthn4j-spring-security, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebAuthn4J Spring Security provides Web Authentication specification support for Spring applications. Affected versions are subject to improper signature counter value handling. 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. This issue has been addressed in version `0.9.1.RELEASE`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-45669?

2 open source packages ship an affected version, including com.webauthn4j:webauthn4j-spring-security-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.webauthn4j:webauthn4j-spring-security-core` | Maven | All versions | 0.9.1.RELEASE |
| `com.webauthn4j:webauthn4j-spring-security-core` | Maven | All versions | 0.9.1.RELEASE |

Products: Webauthn4j Spring Security.

## How do I fix CVE-2023-45669?

Upgrade com.webauthn4j:webauthn4j-spring-security-core to 0.9.1.RELEASE or later.

## Is CVE-2023-45669 being exploited?

There is no known exploitation of CVE-2023-45669 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45669 and fix it if it is affected.

What it is: CVE-2023-45669 is a medium-severity vulnerability in webauthn4j-spring-security, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45669 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.webauthn4j:webauthn4j-spring-security-core (Maven): affected all versions; fixed in 0.9.1.RELEASE
- com.webauthn4j:webauthn4j-spring-security-core (Maven): affected all versions; fixed in 0.9.1.RELEASE

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-45669/ (Markdown: https://insights.sbomify.com/CVE-2023-45669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45669
- OSV: https://osv.dev/vulnerability/CVE-2023-45669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-45669/
Summaries are generated and may contain mistakes; the official description above is the record.