CVE-2023-45844
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 · uneditedThe vulnerability allows a low privileged user that have access to the device when locked in Kiosk mode to install an arbitrary Android application and leverage it to have access to critical device settings such as the device power management or eventually the device secure settings (ADB debug).
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 confidenceA low-privileged user with physical access to a device locked in Kiosk mode can bypass the intended restrictions to install arbitrary Android applications. This Kiosk mode escape enables access to critical device settings including power management and ADB debug functionality.
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 dataall versionsall versionsall versionsCVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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.
-
Identify the device modelCheck the physical device label or system information to confirm the exact model number (WR2107, WR2110, or WR2115)Affected if The device is any of these three models - all versions are affected by this CVE
-
Confirm Kiosk mode is configuredAccess the device admin or mobility management settings and verify if Kiosk mode or single-app mode restrictions are enabledAffected if Kiosk mode is active on the device - the bypass specifically targets this mode
-
Verify app installation settingsCheck if the device allows installation of applications from sources outside an approved enterprise app store, or if side-loading is enabled in developer or security settingsAffected if Side-loading or installation from unknown sources is permitted while in Kiosk mode
-
Check ADB debugging statusInspect the developer options or USB debugging settings to determine if ADB debugging is enabled on the deviceAffected if ADB debugging is turned on - the vulnerability grants access to this functionality
-
Assess user account privilegesDetermine if the current user session is a standard or restricted user account rather than a full administrator accountAffected if The exploiting user has only low or standard privileges - this is a required condition for the CVE
A user is affected if they have one of the three affected Boschrexroth Ctrlx HMI Web Panel models with Kiosk mode enabled, and a low-privileged user with physical access could exploit the bypass to install arbitrary apps and enable ADB debugging.
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.
From vendor dataRestrict application installation in Kiosk mode by enforcing whitelist policies and disabling side-loading; disable developer options and ADB debugging when not required for managed device deployments.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45844 — 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-45844 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