CVE-2022-36830
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 cancelAlarmManager in Charm by Samsung prior to version 1.2.3 allows local attackers to access files without permission via implicit intent.
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 confidencePendingIntent hijacking vulnerability in the cancelAlarmManager function of Samsung Charm app (versions prior to 1.2.3). The function improperly uses implicit intents with PendingIntents, allowing a local attacker to intercept or manipulate these intents to bypass permission checks and access files without 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< 1.2.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check Samsung Charm app versionNavigate to Settings > Apps > Samsung Charm (or check via the app's About section) and note the installed version numberAffected if The installed version is lower than 1.2.3
-
Verify cancelAlarmManager function is presentDecompile or inspect the Samsung Charm APK and locate the cancelAlarmManager function within the app codeAffected if The cancelAlarmManager function exists and uses PendingIntent with implicit intents (without specifying package name or using FLAG_IMMUTABLE)
-
Inspect PendingIntent configurationExamine the PendingIntent creation code in the cancelAlarmManager function for use of implicit intents (Intent without setPackage or setComponent) and absence of FLAG_IMMUTABLE/FLAG_EXCLUDE_CURRENT_OPTIONS flagsAffected if PendingIntents are created with implicit intents lacking explicit component/package definitions and missing security flags like FLAG_IMMUTABLE
A user is affected if the Samsung Charm firmware version is below 1.2.3 AND the app contains the vulnerable cancelAlarmManager function using improperly secured PendingIntents with implicit intents.
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 · scoped1.2.3
Upgrade Samsung Charm to version 1.2.3 or later, which contains the fix for this PendingIntent hijacking vulnerability.
Charm Firmware 1.2.3
- Check the current version of Charm installed on the Samsung device via Settings > Apps > Charm
- Open Samsung Galaxy Store or Samsung's official app store
- Search for Charm and verify the available version
- If installed version is below 1.2.3, tap Update to install version 1.2.3 or later
- Confirm the update completed successfully and verify the new version in app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36830 — 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-36830 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