dbcve.org
AndroidOperating system · Google

CVE-2022-33732

HIGH · 7.1 CVSS v3.1 Published 2022-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
Improper access control vulnerability in Samsung Dex for PC prior to SMR Aug-2022 Release 1 allows local attackers to scan and connect to PC by unprotected binder call.

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 confidence

This vulnerability in Samsung Dex for PC allows local attackers to scan and connect to a PC due to improper access control in an unprotected Android binder call. The flaw enables unauthorized external connections without proper authentication, potentially letting a local attacker establish a Dex session on a connected PC.

MitigationApply the SMR August-2022 Release 1 security update or later for Samsung Dex for PC, which implements proper access controls on the binder interface to prevent unauthorized scanning and connections.

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
AndroidOperating system
Affected:= 12.0

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
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify Android version is 12.0
    Check the device system settings or use 'adb shell getprop ro.build.version.release' to confirm the installed Android version equals 12.0
    Affected if Android version is exactly 12.0 and no security patches after August 2022 have been applied
  2. Confirm Samsung Dex for PC application is installed
    Check for the Samsung Dex for PC app package (com.sec.android.app.desktoplauncher or similar Dex-related packages) using 'adb shell pm list packages' or via device settings
    Affected if Samsung Dex for PC app is installed on the Android 12.0 device
  3. Verify Dex for PC is enabled or has been configured
    Check device settings under Samsung Dex or Desktop Mode settings, or inspect running Dex-related processes using 'adb shell ps -A | grep -i dex'
    Affected if Dex for PC feature has been enabled or configured on the device
  4. Inspect binder interface access controls
    Examine binder transactions related to Dex service using debugging tools or security logs to identify if the binder call interface lacks proper access control checks
    Affected if The binder interface for Dex allows unauthenticated external connection requests without proper validation

A user is affected if running Android 12.0 with Samsung Dex for PC installed and enabled, and the device has not received the August-2022 Samsung security update that adds proper access controls to the binder interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SMR August-2022 Release 1 security update or later for Samsung Dex for PC, which implements proper access controls on the binder interface to prevent unauthorized scanning and connections.

Recommended fix Moderate confidence

Samsung Android 12.0 with SMR Aug-2022 Release 1 or later

  1. Check current Android version and security patch level on the device in Settings > About Phone > Software Information
  2. Apply the August 2022 Samsung security update (SMR Aug-2022 Release 1) through Settings > Software Update > Download and Install
  3. Verify the security patch level shows August 2022 or later after the update completes

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33732 — 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-33732 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