CVE-2023-51772
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 · uneditedOne Identity Password Manager before 5.13.1 allows Kiosk Escape. This product enables users to reset their Active Directory passwords on the login screen of a Windows client. It launches a Chromium based browser in Kiosk mode to provide the reset functionality. The escape sequence is: wait for a session timeout, click on the Help icon, observe that there is a browser window for the One Identity website, navigate to any website that offers file upload, navigate to cmd.exe from the file explorer window, and launch cmd.exe as NT AUTHORITY\SYSTEM.
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 confidenceOne Identity Password Manager before 5.13.1 allows authenticated users to escape Chromium Kiosk mode through the help function. By waiting for session timeout, clicking Help, navigating to file upload websites, and accessing cmd.exe, attackers can launch commands as NT AUTHORITY\SYSTEM, achieving full privilege escalation from Kiosk-restricted session to system-level execution.
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< 5.13.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check One Identity Password Manager versionLocate the Password Manager installation directory and check the version information in the application properties, or use the software inventory/control panel to view installed programs. Compare the version number to the affected range (anything below 5.13.1).Affected if The installed version is below 5.13.1
-
Verify Kiosk mode is configuredReview the Password Manager configuration files (typically in the installation directory or config folder) for Kiosk mode settings. Look for KioskEnabled, KioskMode, or similar configuration parameters.Affected if Kiosk mode is enabled in the configuration
-
Confirm help function accessibility in Kiosk sessionsExamine the Kiosk mode configuration to determine whether the help function (Help button/menu) remains accessible after session timeout. Check for settings controlling Help menu availability in locked-down sessions.Affected if The help function is accessible within the Kiosk-restricted session after timeout
-
Inspect Kiosk session timeout behaviorReview the session timeout configuration settings in the Password Manager admin console or configuration files. Determine whether the session remains in a partially interactive state after timeout that could allow help function access.Affected if Sessions remain interactive or partially accessible after timeout rather than fully locking out
You are affected if One Identity Password Manager version is below 5.13.1 AND Kiosk mode is enabled with the help function remaining accessible after session timeout, allowing a restricted user to escape to system-level command execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.13.1
Upgrade to One Identity Password Manager 5.13.1 or later, and review Kiosk mode configuration to ensure file system and command execution paths are properly restricted even if session timeout occurs.
5.13.1
- Identify the current installed version of One Identity Password Manager
- Download One Identity Password Manager version 5.13.1 or later from the official One Identity support portal
- Follow One Identity's documented upgrade procedure to apply the update to the Password Manager server and/or client components
- Verify the upgrade was successful by confirming the installed version is 5.13.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51772 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51772 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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