Improper AuthenticationWeakness · CWE-287

CVE-2024-12310

HIGH · 7.0 CVSS v4.0 Published 2025-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
No privileges 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
A vulnerability in Imprivata Enterprise Access Management (formerly Imprivata OneSign) allows bypassing the login screen of the shared kiosk workstation and allows unauthorized access to the underlying Windows system through the already logged-in autologon account due to insufficient handling of keyboard shortcuts. This issue affects Imprivata Enterprise Access Management versions 5.3 through 24.2.

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 · high confidence

Imprivata Enterprise Access Management (versions 5.3-24.2) contains an authentication bypass vulnerability in its kiosk mode functionality. Attackers can bypass the login screen on shared kiosk workstations by leveraging insufficiently handled keyboard shortcuts, allowing unauthorized access to the underlying Windows system using the already logged-in autologon account.

MitigationApply vendor patch (version 24.3 or later) to all affected Imprivata Enterprise Access Management installations. As a compensating control, physically secure keyboard access on kiosk workstations until the patch is deployed.

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

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
Physical
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify Imprivata Enterprise Access Management is installed
    Check for Imprivata Enterprise Access Management in the installed programs list (Windows Control Panel > Programs and Features, or run 'Get-Package' in PowerShell to list installed software)
    Affected if The software is present on the system and the version falls within 5.3 to 24.2
  2. Confirm the installed version number
    Locate the installed version by checking the software's About dialog, installation directory for a version file, or using the vendor's configuration/management console to query the agent version
    Affected if The version number is 5.3, 5.4, 5.5, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, 18.x, 19.x, 20.x, 21.x, 22.x, 23.x, 24.0, 24.1, or 24.2 (any version from 5.3 through 24.2)
  3. Determine if kiosk mode functionality is enabled
    Check the Imprivata management console or local agent configuration for kiosk mode settings; look for profiles or policies that enable workstation lockdown or kiosk mode behavior
    Affected if Kiosk mode or workstation lockdown is active on the target machine
  4. Inspect kiosk mode keyboard shortcut configuration
    Review the Imprivata kiosk mode policy settings for allowed or configured keyboard shortcuts; check if the management console exposes shortcut handling controls
    Affected if Kiosk mode is enabled and keyboard shortcuts are not properly restricted or filtered
  5. Review security event logs for unauthorized kiosk bypass attempts
    Examine Windows Security Event Logs and Imprivata audit logs for events indicating kiosk lockout bypass, unexpected session transitions, or privilege escalation from kiosk to Windows desktop
    Affected if Kiosk mode is enabled and logs show unauthorized access to the underlying Windows session using keyboard shortcuts

You are affected if Imprivata Enterprise Access Management version 5.3 through 24.2 is installed with kiosk mode enabled on the workstation, as the authentication bypass via keyboard shortcuts only applies when the vulnerable kiosk functionality is in use.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch (version 24.3 or later) to all affected Imprivata Enterprise Access Management installations. As a compensating control, physically secure keyboard access on kiosk workstations until the patch is deployed.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-12310 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