External risk intelligence

Webauthn Framework Authentication Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2021-38299

The vulnerability affects a Webauthn framework, which is designed to be integrated into web applications and identity portals to handle authentication. As these frameworks are typically used to implement public-facing web login endpoints, the vulnerable code is commonly positioned at the internet edge to interact with users and their FIDO2 authenticators.

Authentication Bypass

Spomky Labs Webauthn Framework

3.3.0 to before 3.3.4before 3.2.9

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in the Webauthn Framework, identified as CVE-2021-38299, involves incorrect access control that could allow an attacker to bypass user presence checks when using a FIDO2 authenticator. This could potentially enable unauthorized access to systems that rely on this framework for authentication. The main concern is confirming relevance and exposure for any services utilizing this specific software.

  • Bypass authentication checks without user interaction.
  • Potential unauthorized access to authenticated services.
  • Confirm if your systems use this authentication software.

Attack Path

How an attacker could exploit the issue

An attacker who compromises a user's system can bypass security checks when logging into a vulnerable service. By using a connected FIDO2 authenticator, they can authenticate without the required user presence verification. This vulnerability could potentially allow unauthorized access to sensitive information or system functions.

  • Attacker controls user's system.
  • FIDO2 authenticator used for login.
  • Risk of unauthorized access and data compromise.

Live Threat

Current exploitation, exposure, and threat context

Incorrect access control in the Webauthn Framework could allow an attacker with control of a user's system to bypass user presence checks when logging in using a FIDO2 authenticator. This could affect services that rely on the framework for authentication, potentially leading to unauthorized access.

  • User accounts and sessions at risk.
  • Bypasses user presence checks.
  • Unauthorized access to services.

Operational Fix

Recommended remediation, mitigation, and detection steps

In real-world scenarios, application owners are likely responsible for addressing this vulnerability within the Webauthn Framework, as it directly impacts authentication. The first practical step involves identifying all instances of the affected technology, assessing their exposure and business criticality, and then confirming the accountable owner for remediation planning.

  • Application owners should manage this issue.
  • Verify reachability and business criticality first.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Spomky-Labs Webauthn Framework?

The Webauthn Framework is a software library that allows developers to add FIDO2-based authentication to their web applications. It acts as a bridge between a web server and a user's security key or hardware authenticator, helping process the cryptographic challenges required to verify a user's identity.

What is the vulnerability in CVE-2021-38299?

This vulnerability is classified as CWE-287, or Incorrect Access Control. Specifically, the framework fails to properly verify the 'user presence' signal from a FIDO2 authenticator. This means the system assumes a physical interaction occurred with the security key even if one did not, allowing the authentication process to proceed incorrectly.

How does an attacker trigger this flaw?

An attacker must already have control over the user's system to exploit this. With that access, they can manipulate the authentication flow when the user attempts to log in using a FIDO2 device. Note that this bug does not allow someone to bypass authentication remotely without first compromising the local environment where the authenticator is used.

Is my organization at risk from this CVE?

According to Halo Surface Signal, this software is typically deployed at the internet edge to handle user logins. If your web applications use the vulnerable versions of the Webauthn Framework to manage identity, those services are likely exposed to this risk. You should check your application dependencies to see if they include the affected library versions.

What should I do if I use this framework?

Start by auditing your application codebase to identify any use of the Spomky-Labs Webauthn Framework and confirm the version in use. Once identified, work with the application owners to assess the service's criticality and prioritize updating to a patched version, as this is a core component of your security authentication flow.

References