CVE-2022-33704
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 · uneditedImproper validation vulnerability in ucmRetParcelable of KnoxSDK prior to SMR Jul-2022 Release 1 allows attackers to launch certain activities.
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 confidenceThis is an improper validation vulnerability in the ucmRetParcelable function within Samsung's KnoxSDK. The lack of proper input validation in this parcelable-related component (used for Android inter-process communication) allows attackers to launch certain activities on affected devices. This affects KnoxSDK versions prior to the July 2022 SMR release.
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 the Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version is 10.0, 11.0, or 12.0 (this is a prerequisite for being in the affected scope)
-
Verify Samsung KnoxSDK is installedCheck for Knox-related system apps or packages. On Samsung devices, look for 'com.sec.knox' or 'com.samsung.android.knox' in the package list via 'adb shell pm list packages | grep knox'Affected if KnoxSDK packages are present on the device
-
Determine the installed KnoxSDK versionCheck the Knox version via 'adb shell dumpsys package com.samsung.android.knox' or look in Settings > Apps > Knox > VersionAffected if The KnoxSDK version predates the July 2022 SMR release (patched version is SMR Jul-2022 Release 1 or later)
-
Confirm Knox is active and ucmRetParcelable feature is enabledVerify Knox is provisioned and active by checking 'adb shell dumpsys package com.samsung.android.knox' for active license state or check if UCM (Unified Credential Manager) service is runningAffected if Knox is enabled and the ucmRetParcelable parcelable component is accessible to applications
A device is affected if it runs Android 10, 11, or 12, has Samsung KnoxSDK installed with a version earlier than the July 2022 SMR release, and has Knox features enabled.
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 · scopedUpdate KnoxSDK to SMR Jul-2022 Release 1 or later to obtain the patched version with proper validation in ucmRetParcelable.
SMR Jul-2022 Release 1
- Identify if the device uses Samsung KnoxSDK
- Check current KnoxSDK version on the device
- Update to SMR Jul-2022 Release 1 or later which contains the fix for the ucmRetParcelable improper validation vulnerability
- Verify the update was successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33704 — 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-33704 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