CVE-2023-42543
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 · uneditedImproper verification of intent by broadcast receiver vulnerability in Bixby Voice prior to version 3.3.35.12 allows attackers to access arbitrary data with Bixby Voice privilege.
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 a broadcast receiver vulnerability in Samsung's Bixby Voice assistant where the receiver fails to properly verify incoming intents, allowing malicious actors to send crafted broadcasts that Bixby Voice processes with its elevated privileges, resulting in unauthorized access to arbitrary data.
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< 3.3.35.12CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Bixby Voice is installedCheck for the Bixby Voice app on the Samsung device. On Android, this can be done via: Settings > Apps > Bixby Voice, or by running 'adb shell pm list packages | grep bixby'Affected if Bixby Voice package is present on the device
-
Retrieve installed Bixby Voice versionNavigate to Settings > Apps > Bixby Voice > App info, or use 'adb shell dumpsys package com.samsung.android.bixby.agent' to retrieve the versionName from the package infoAffected if Unable to retrieve version information or app is not installed
-
Compare version against affected rangeCompare the installed version number to the affected range: versions prior to 3.3.35.12 are vulnerableAffected if Installed version is less than 3.3.35.12 (e.g., 3.3.34.5, 3.2.15.0, etc.)
-
Check broadcast receiver accessibility (optional)Use 'adb shell dumpsys package com.samsung.android.bixby.agent' to examine if the Bixby Voice broadcast receivers are exported, which would indicate the vulnerable attack surface is presentAffected if Broadcast receivers are exported without proper permission checks
User is affected if Bixby Voice is installed and the installed version is lower than 3.3.35.12, making the unpatched broadcast receiver accessible to malicious 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 · scoped3.3.35.12
Update Bixby Voice to version 3.3.35.12 or later to obtain the patched broadcast receiver that properly validates intent sources.
Bixby Voice version 3.3.35.12 or later
- Open Galaxy Store or Google Play Store on your Samsung device
- Search for Bixby Voice
- Install or update Bixby Voice to version 3.3.35.12 or later
- Verify the installed version in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42543 — 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-42543 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