dbcve.org
AndroidOperating system · Samsung

CVE-2024-49413

HIGH · 7.8 CVSS v3.1 Published 2024-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Verification of Cryptographic Signature in SmartSwitch prior to SMR Dec-2024 Release 1 allows local attackers to install malicious applications.

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 confidence

Improper verification of cryptographic signatures in Samsung SmartSwitch prior to the December 2024 security maintenance release allows local attackers to bypass signature validation and install malicious applications. This is a local privilege escalation vulnerability where the app installer fails to properly validate the cryptographic signature on application packages before installation.

MitigationUpdate SmartSwitch to the SMR Dec-2024 Release 1 or later which contains the proper signature verification fix. Avoid installing applications from untrusted sources in the interim.

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:= 13.0= 14.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
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The device runs Android 13.0 or Android 14.0 specifically
  2. Confirm SmartSwitch is installed
    Check for SmartSwitch app in the app drawer, or run 'pm list packages | grep smartswitch' via ADB shell
    Affected if SmartSwitch app is present on the device
  3. Check SmartSwitch app version
    Go to Settings > Apps > SmartSwitch > App info > Version, or run 'dumpsys package com.sec.android.app.samsungapps' via ADB shell to find versionName
    Affected if Version is earlier than the SMR Dec-2024 Release 1 update (version date December 2024 or earlier)
  4. Determine if app installation from untrusted sources is possible
    Go to Settings > Apps > SmartSwitch > Install unknown apps, or check if 'Settings > Security and privacy > Install unknown apps' allows SmartSwitch
    Affected if SmartSwitch is permitted to install apps from unknown sources

The device is affected if it runs Android 13.0 or 14.0, has SmartSwitch installed, and the SmartSwitch version predates the December 2024 security update.

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

Update SmartSwitch to the SMR Dec-2024 Release 1 or later which contains the proper signature verification fix. Avoid installing applications from untrusted sources in the interim.

Recommended fix Moderate confidence

SMR Dec-2024 Release 1

  1. Navigate to Settings > Software update (or Settings > Security and privacy on Samsung devices)
  2. Check for and download the SMR Dec-2024 Release 1 security update
  3. Install the security update and restart the device
  4. Verify the update was installed by checking the Android security patch level in Settings > About phone > Software information

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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