CVE-2023-42555
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 · uneditedUse of implicit intent for sensitive communication vulnerability in EasySetup prior to version 11.1.13 allows attackers to get the bluetooth address of user device.
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 vulnerability in Samsung's EasySetup component where implicit intents are used to transmit the Bluetooth MAC address (a persistent hardware identifier). Because implicit intents can be intercepted by any app listening for that intent action on the device, a malicious application can receive the Bluetooth address without proper 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< 11.1.13CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Find EasySetup package nameRun 'adb shell pm list packages | grep -i easysetup' or check in Settings > Apps for an app named 'EasySetup' or 'Samsung EasySetup'Affected if No package found means the app is not installed and the user is not affected
-
Check installed version of EasySetupIn Settings > Apps > EasySetup, look at the version number under 'App info', or run 'adb shell dumpsys package <package_name>' and read the versionNameAffected if Version number is less than 11.1.13 (for example 11.1.12, 11.1.10, 10.x.x, etc.) indicates the vulnerable version is installed
-
Confirm app has been usedIn Settings > Apps > EasySetup, check 'Usage' or 'Last used' to see if the app has recent activity, indicating it may have transmitted data via the vulnerable intent mechanismAffected if App shows recent usage and version is below 11.1.13, meaning the vulnerable code path was likely executed
User is affected if Samsung EasySetup is installed with a version lower than 11.1.13 and has been used, allowing implicit intents to potentially leak the Bluetooth MAC address to malicious apps.
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 · scoped11.1.13
Upgrade EasySetup to version 11.1.13 or later, which replaces implicit intents with explicit intents that target only the intended receiver application.
11.1.13
- Check the current version of EasySetup installed on your Samsung device
- Upgrade EasySetup to version 11.1.13 or later through the Samsung Galaxy Store, Google Play Store, or device settings
- Verify the upgrade was successful by confirming the new version in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42555 — 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-2023-42555 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