CVE-2022-33734
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 · uneditedSensitive information exposure in onCharacteristicChanged in Charm by Samsung prior to version 1.2.3 allows attacker to get bluetooth connection information 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 confidenceA sensitive information exposure vulnerability exists in the onCharacteristicChanged callback handler in Samsung's Charm Bluetooth app. The callback improperly exposes Bluetooth connection information to unauthorized callers without performing proper permission validation, allowing attackers to obtain sensitive connection details.
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 if Samsung Charm app is installedOn the Samsung device, go to Settings > Apps > Downloaded apps, or use adb shell pm list packages to list installed packages. Look for package name 'com.samsung.android.charm' or 'Samsung Charm' in the app list.Affected if The app is present on the device
-
Determine installed version of Samsung CharmIn Settings > Apps > Downloaded apps > Samsung Charm, view the 'Version' information displayed under the app name. Alternatively, use adb shell dumpsys package com.samsung.android.charm to retrieve version details from the package manager.Affected if Version number cannot be determined or shows below 1.2.3
-
Verify Bluetooth functionality is in useCheck if Bluetooth is enabled on the device and if Samsung Charm is actively monitoring or collecting Bluetooth device information. The vulnerability in onCharacteristicChanged only affects environments where Bluetooth LE communication is active.Affected if Bluetooth is enabled and Charm is actively running with Bluetooth monitoring
User is affected if Samsung Charm app is installed with a version lower than 1.2.3 and the app is using Bluetooth functionality.
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 Charm by Samsung to version 1.2.3 or later, which contains the fix for the improper permission check in the onCharacteristicChanged callback.
1.2.3
- Open the Galaxy Store or Google Play Store on the Samsung device
- Search for "Charm" by Samsung
- Locate the Charm application and tap Update
- Verify the updated version is 1.2.3 or higher by checking the app version in Settings > Apps > Charm > Version information
- Confirm the update has been applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33734 — 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-33734 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