dbcve.org
Smart SwitchApplication · Samsung

CVE-2025-20996

MEDIUM · 5.0 CVSS v3.1 Published 2025-06-04
Fix available
A fix is available. Upgrade to 3.7.64.10 or later.
See remediation →
50/100
Remediation priority · Moderate

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 authorization in Smart Switch installed on non-Samsung Device prior to version 3.7.64.10 allows local attackers to read data with the privilege of Smart Switch. User interaction is required for triggering this vulnerability.

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

Improper authorization in Smart Switch on non-Samsung devices prior to version 3.7.64.10 allows local attackers to read data accessible to the Smart Switch application. The vulnerability requires user interaction to trigger, suggesting the attacker tricks the victim into performing an action that exploits the authorization flaw to access restricted data.

MitigationUpdate Smart Switch to version 3.7.64.10 or later. Until then, avoid running Smart Switch and be cautious of any unexpected prompts or file operations within the application.

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
Smart SwitchApplication
Affected:< 3.7.64.10

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check if Smart Switch is installed
    Open your device's app drawer or settings > apps and look for 'Smart Switch' or 'Samsung Smart Switch'. On Android, you can also check Google Play Store > My apps > Smart Switch.
    Affected if Smart Switch is found installed on the device
  2. Verify the installed version
    In Smart Switch, go to Settings (three lines menu) > About Smart Switch > check the version number. Alternatively, on Android, open Google Play Store, search for Smart Switch, and view the version under 'Additional information'.
    Affected if The version number displayed is less than 3.7.64.10 (for example, 3.7.64.9, 3.7.50, etc.)
  3. Confirm device type
    Check your device manufacturer. On Android, go to Settings > About Phone > Model or Manufacturer. Smart Switch is pre-installed on Samsung devices but can be downloaded separately on non-Samsung Android devices.
    Affected if The device is NOT a Samsung device (e.g., Google Pixel, OnePlus, Motorola, etc.) and Smart Switch was manually installed from an app store
  4. Assess user interaction exposure
    Consider whether the device could be accessed by other local users or if you have installed Smart Switch files received from untrusted sources. The vulnerability requires tricking the user into performing an action within the app.
    Affected if You share the device with others or you have importedtransfer files into Smart Switch from untrusted sources

You are affected if Smart Switch version is below 3.7.64.10 AND the app is running on a non-Samsung device, as this CVE only impacts manually-installed Smart Switch on non-Samsung hardware.

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 3.7.64.10 or later
Fixed in 3.7.64.10
Interim mitigation

Update Smart Switch to version 3.7.64.10 or later. Until then, avoid running Smart Switch and be cautious of any unexpected prompts or file operations within the application.

Recommended fix High confidence

Smart Switch version 3.7.64.10

  1. Open the Galaxy Store app on your Samsung device
  2. Search for 'Smart Switch' in the Galaxy Store
  3. If an update is available, tap 'Update' to install Smart Switch version 3.7.64.10 or later
  4. Alternatively, open Google Play Store, search for 'Smart Switch', and update if a newer version is available
  5. After updating, verify the installed version by opening Smart Switch and checking the app settings or about section

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

Fix this in Smart Switch Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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