CVE-2022-25814
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 · uneditedPendingIntent hijacking vulnerability in Wearable Manager Installer prior to SMR Mar-2022 Release 1 allows local attackers to perform unauthorized action without permission via hijacking the PendingIntent.
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 confidencePendingIntent hijacking vulnerability in Samsung's Wearable Manager Installer allows a local attacker to intercept and misuse an improperly secured PendingIntent to perform unauthorized actions with the application's privileges. This is a privilege escalation issue where the vulnerable app's PendingIntent can be captured by a malicious local app.
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= 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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device is running Android 11.0 or 12.0 exactly (these are the only affected versions listed)
-
Locate Samsung Wearable Manager InstallerCheck installed apps list in Settings > Apps, or run 'pm list packages | grep wearable' via ADB shellAffected if The app named 'Wearable Manager Installer' or similar Samsung wearable installer package is present on the device
-
Identify installed app versionIn Settings > Apps > Wearable Manager Installer > App info, note the version; or run 'dumpsys package <package_name>' via ADB to retrieve versionInfoAffected if A version is returned - any version combined with Android 11.0/12.0 indicates potential exposure since the patch status is unknown
-
Verify patch installation statusCheck device security patch level in Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if The security patch level is earlier than March 2022, indicating the vendor fix has not been applied
The device is affected if it runs Android 11.0 or 12.0, has the Samsung Wearable Manager Installer app installed, and has a security patch level before March 2022.
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 Mar-2022 Release 1 or later security update to affected devices to obtain the vendor patch that properly secures the PendingIntent.
SMR Mar-2022 Release 1 or later
- Check for system updates on your Samsung device running Android 11.0 or 12.0
- Navigate to Settings > Software Update
- Download and install the SMR (Samsung Mobile Security) March-2022 Release 1 update or later
- Ensure the Wearable Manager Installer app is updated as part of the system update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25814 — 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-25814 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