dbcve.org
Charm FirmwareOperating system · Samsung

CVE-2022-36829

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 1.2.3 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
PendingIntent hijacking vulnerability in releaseAlarm 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 · high confidence

This is a PendingIntent hijacking vulnerability in Samsung's Charm app (version prior to 1.2.3). The releaseAlarm function creates a mutable PendingIntent with an implicit intent, allowing a local malicious app to intercept or modify the intent and gain unauthorized file access permissions.

MitigationUpdate Charm by Samsung to version 1.2.3 or later. If patching the code directly, ensure PendingIntents are created with FLAG_IMMUTABLE and use explicit intents instead of implicit intents.

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
Charm FirmwareOperating system
Affected:< 1.2.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Samsung Charm app installation
    On the Android device, go to Settings > Apps > Apps, then search for 'Charm' or 'Samsung Charm'. Alternatively, run 'adb shell pm list packages | grep -i charm' to list installed packages.
    Affected if The Charm app is installed on the device.
  2. Determine installed Charm version
    In Settings > Apps > Charm > App info, note the version number shown under the app name. Or run 'adb shell dumpsys package <package_name>' and look for versionName in the package info.
    Affected if The displayed version is a number less than 1.2.3 (e.g., 1.2.2, 1.2.1, 1.0.0).
  3. Verify app is a Samsung pre-installed app
    Check if Charm came pre-loaded on the device or was installed from Samsung's ecosystem. Run 'adb shell pm list packages -3 | grep samsung' to see Samsung-supplied packages.
    Affected if The Charm app is from Samsung's firmware distribution and version is below 1.2.3.
  4. Confirm releaseAlarm functionality exists
    Decompile the APK (if available) and inspect the releaseAlarm function for PendingIntent creation. Look for PendingIntent.getBroadcast or PendingIntent.getActivity calls without FLAG_IMMUTABLE.
    Affected if The app code contains a mutable PendingIntent in the releaseAlarm function (PendingIntent without FLAG_IMMUTABLE flag).

A user is affected if Samsung Charm app is installed with a version number lower than 1.2.3, as this version range contains the vulnerable mutable PendingIntent in the releaseAlarm function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2.3 or later
Fixed in 1.2.3
Interim mitigation

Update Charm by Samsung to version 1.2.3 or later. If patching the code directly, ensure PendingIntents are created with FLAG_IMMUTABLE and use explicit intents instead of implicit intents.

Recommended fix High confidence

1.2.3

  1. Open the Settings app on your Samsung device
  2. Navigate to Settings > Software Update (or System > Software Update depending on device)
  3. Tap on Check for updates or Download and install
  4. Ensure the Charm application or device firmware updates to version 1.2.3 or later
  5. After update, verify the Charm version in Settings > Apps > Charm to confirm version 1.2.3 is installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Charm Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36829 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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