CVE-2022-33695
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 · uneditedUse of improper permission in InputManagerService prior to SMR Jul-2022 Release 1 allows unauthorized access to the service.
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 confidenceThe InputManagerService on Samsung devices prior to the July 2022 SMR contains an improper permission check that allows unauthorized processes to access the service's functions. This could enable a malicious application to potentially inject input events, manipulate touch/keystrokes, or interact with the input system without proper authorization.
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= 10.0= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device manufacturerCheck if the device is a Samsung device by reviewing the device settings or using 'getprop ro.product.manufacturer' command in ADBAffected if Device is not a Samsung device (this CVE specifically affects Samsung implementations)
-
Check Android versionVerify the Android version by going to Settings > About Phone > Android version or using 'getprop ro.build.version.release' in ADBAffected if Android version is 10.0, 11.0, or 12.0 (these are the affected versions per the CVE data)
-
Check Samsung SMR patch levelCheck the Samsung Security Maintenance Release patch date in Settings > About Phone > Software information > Build number, or use 'getprop ro.build.version.sem' in ADB to identify the SMR dateAffected if SMR patch level is prior to July 2022 Release 1 (the vulnerability was fixed in the July 2022 SMR)
-
Verify InputManagerService accessibilityThis requires examining system service logs or using security auditing tools to determine if unauthorized processes can access InputManagerService functions - typically requires root or professional security toolingAffected if Non-system processes without INPUT_DEVICE permission can access InputManagerService methods (the core vulnerability condition)
A Samsung device running Android 10.0, 11.0, or 12.0 with an SMR patch level before July 2022 is likely affected by this improper permission check in InputManagerService.
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 · scopedApply the Samsung SMR July-2022 Release 1 or later patch to affected devices. Users should ensure their Samsung devices are running the latest security maintenance release.
SMR Jul-2022 Release 1 (July 2022 Samsung Security Patch)
- Navigate to Settings > Software Update on your Samsung Galaxy device
- Tap 'Download and install' to check for the July 2022 SMR (Samsung Mobile Security) update
- If available, install the update to patch the improper permission vulnerability in InputManagerService
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33695 — 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-33695 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