CVE-2021-38299 json
Improper Access Control in Webauthn Framework
published 2021-09-27 5 y ago modified 2026-11-05 3 d ago also GHSA-6whf-q6p5-84wg , EUVD-2021-1997
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Webauthn Framework 3.3.x before 3.3.4 has Incorrect Access Control. An attacker that controls a user's system is able to login to a vulnerable service using an attached FIDO2 authenticator without passing a check of the user presence.
Patch / fix
- packagist web-auth/webauthn-framework 3.3.4
- spomky-labs webauthn_framework 3.3.4
- spomky-labs webauthn_framwork 3.2.9
Exploit prediction
1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | web-auth/webauthn-framework | >=3.3.0, <3.3.4 |
3.3.4 |
Classification
References
-
github.com
/web-auth/webauthn-framework/commit/572e239c5702667ca52487faf861abc768a46308
web
-
github.com
/web-auth/webauthn-framework/releases
web, release-notes, third-party-advisory
-
fzi.de
/en/news/news/detail-en/artikel/fsa-2021-1-fehlende-ueberpruefung-von-user-presence-in-webauthn-framework/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-38299
advisory
-
github.com
/web-auth/webauthn-framework
package
-
github.com
/web-auth/webauthn-framework/releases/tag/v3.3.4
web
-
fzi.de
/en/news/news/detail-en/artikel/fsa-2021-1-fehlende-ueberpruefung-von-user-presence-in-webauthn-framework
web
Sources
- CVE List CVE-2021-38299
- GitHub Advisory GHSA-6whf-q6p5-84wg
- NVD CVE-2021-38299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.