CVE-2022-36441
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 · uneditedAn issue was discovered in Zebra Enterprise Home Screen 4.1.19. The Gboard used by different applications can be used to launch and use several other applications that are restricted by the admin.
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 confidenceZebra Enterprise Home Screen 4.1.19 fails to properly restrict application launching through the Gboard keyboard, allowing users to bypass admin-imposed application restrictions and launch applications that should be blocked by enterprise mobility management policies.
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= 4.1.19CVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 Zebra Enterprise Home Screen versionCheck the installed version of Zebra Enterprise Home Screen on the device. This can typically be done via the device's Settings > Apps > Zebra Enterprise Home Screen, or by querying the package manager via ADB: `adb shell dumpsys package com.zebra.homescreen | grep versionName`Affected if The installed version is exactly 4.1.19 (this is the only affected version per the CVE)
-
Confirm Gboard keyboard is enabledNavigate to Settings > Language & Input > Virtual Keyboard on the Zebra device, or use ADB: `adb shell settings get secure default_input_method` to check if Gboard is set as the default input methodAffected if Gboard (com.google.android.inputmethod.latin) is the active or default keyboard input method
-
Verify application launch restrictions are configuredCheck if Zebra Enterprise Home Screen has application whitelist/blacklist restrictions enabled. This is typically configured through EMM (Enterprise Mobility Management) policies or Zebra staging configurations. Review the kiosk mode or app launcher settings.Affected if Application launch restrictions are intended to be enforced via Zebra Enterprise Home Screen policies
-
Test application launch bypass via GboardWith Gboard as the active keyboard, attempt to search for and launch an application that should be blocked by existing enterprise restrictions. Use Gboard's app search feature to see if blocked applications appear and can be launched.Affected if Applications that should be blocked by enterprise mobility management policies can be launched through Gboard search
The environment is affected if Zebra Enterprise Home Screen version 4.1.19 is installed, Gboard keyboard is enabled, application launch restrictions are configured, AND blocked applications can be launched through Gboard's search interface.
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 dataUpdate Zebra Enterprise Home Screen to the latest patched version and verify that application launch restrictions are properly enforced through the keyboard interface.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36441 — 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-2022-36441 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