CVE-2022-22264
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 sanitization of incoming intent in Dressroom prior to SMR Jan-2022 Release 1 allows local attackers to read and write arbitrary files without permission.
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 confidenceThis is an Android intent handling vulnerability in Samsung's Dressroom app. The app fails to properly sanitize incoming intents (inter-component communication messages), allowing a malicious local application to send specially crafted intents that trick Dressroom into reading or writing arbitrary files outside its intended sandbox. This represents a local privilege escalation where the vulnerable app can be leveraged as an attack vector.
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
- 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.
-
Verify Dressroom app is installedRun 'adb shell pm list packages | grep dressroom' or check device settings under Apps for Samsung DressroomAffected if Package com.samsung.android.dressroom is found on the device
-
Retrieve Dressroom app versionRun 'adb shell dumpsys package com.samsung.android.dressroom' and locate the versionName or versionCode fieldAffected if Version is present and can be compared to patched release (SMR Jan-2022 Release 1 or later)
-
Confirm Android OS versionRun 'adb shell getprop ro.build.version.release' or check device settings under About Phone > Android versionAffected if Device runs Android 10.0, 11.0, or 12.0 (the affected OS versions per the CVE)
-
Check if Dressroom is pre-installed or user-installedRun 'adb shell pm list packages -3' to list third-party apps, or check if Dressroom appears in /system/app or /system/priv-appAffected if Dressroom exists on the device regardless of installation source (pre-installed bloatware is still vulnerable)
User is affected if Samsung Dressroom app is installed on a device running Android 10, 11, or 12 and the Dressroom version is earlier than the SMR Jan-2022 Release 1 patch.
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 Dressroom to SMR Jan-2022 Release 1 or later, which contains proper input validation on incoming intent handlers. As a defense-in-depth measure, consider implementing intent permission checks and validating all intent extras before processing.
SMR Jan-2022 Release 1 or later (Samsung Security Patch)
- Navigate to Settings > Software update on your Samsung device
- Check for and install the latest Samsung security update (SMR Jan-2022 Release 1 or later)
- After updating, verify the patch has been applied by checking the Android security patch level in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22264 — 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-22264 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