dbcve.org
VerifyApplication · Okta

CVE-2024-9191

HIGH · 7.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 5.3.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Okta Device Access features, provided by the Okta Verify agent for Windows, provides access to the OktaDeviceAccessPipe, which enables attackers in a compromised device to retrieve passwords associated with Desktop MFA passwordless logins. The vulnerability was discovered via routine penetration testing. Note: A precondition of this vulnerability is that the user must be using the Okta Device Access passwordless feature. Okta Device Access users not using passwordless are not affected, and customers only using Okta Verify on platforms other than Windows, or only using FastPass are not affected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OktaDeviceAccessPipe within the Okta Verify agent for Windows contains a vulnerability that allows an attacker with local code execution on a compromised device to retrieve passwords associated with Desktop MFA passwordless logins. This affects only Windows users who have enabled the Okta Device Access passwordless feature.

MitigationOrganizations should verify whether users have Okta Device Access passwordless feature enabled on Windows and disable it if present; alternatively, await the vendor patch and test after deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VerifyApplication
Affected:>= 5.0.2, < 5.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Okta Verify is installed on Windows
    Open Programs and Features (appwiz.cpl) or check the installation directory for Okta Verify application
    Affected if Okta Verify is not present on the system, the vulnerability does not apply
  2. Determine the installed version of Okta Verify
    Right-click the Okta Verify application, select Properties, then view the Details tab for version information, or run: Get-ItemProperty 'C:\Program Files\Okta\Okta Verify\OktaVerify.exe' | Select-Object -ExpandProperty FileVersion
    Affected if Version is less than 5.0.2 or greater than or equal to 5.3.3, the system is not affected by this CVE
  3. Verify the Okta Device Access passwordless feature is enabled
    Check Windows settings or Okta Verify configuration for the 'Device Access' or 'Passwordless' feature status. This may be visible in Okta Verify settings or through organization policies applied to the device.
    Affected if The Okta Device Access passwordless feature is disabled or not configured, the vulnerability cannot be exploited

A user is affected only if they have Okta Verify installed on Windows with version 5.0.2 through 5.3.2 and have the Okta Device Access passwordless feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.3.3 or later
Fixed in 5.3.3
Interim mitigation

Organizations should verify whether users have Okta Device Access passwordless feature enabled on Windows and disable it if present; alternatively, await the vendor patch and test after deployment.

Recommended fix High confidence

Upgrade to Okta Verify for Windows version 5.3.3 or later

  1. 1. Check current Okta Verify version on Windows by opening the application and navigating to Settings > About, or by opening Programs and Features in Control Panel
  2. 2. Navigate to the official Okta download portal or your organization's software distribution point to obtain Okta Verify version 5.3.3 or later for Windows
  3. 3. If Okta Verify is currently running, close the application completely
  4. 4. Run the installer for the new version with appropriate administrator privileges
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Settings > About to confirm version 5.3.3 or later is installed
  7. 7. For organizations using Okta Device Access passwordless feature, confirm with end users that Desktop MFA passwordless logins continue to function correctly post-upgrade
Caveat Upgrading Okta Verify is generally low-risk; however, organizations should test the new version in a staging environment before broad deployment to ensure compatibility with existing Okta Device Access configurations and any custom MFA policies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Verify Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9191 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data