dbcve.org
AndroidOperating system · Google

CVE-2017-18652

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered on Samsung mobile devices with M(6.0) and N(7.x) software. SVoice allows arbitrary code execution by changing dynamic libraries. The Samsung ID is SVE-2017-9299 (September 2017).

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

SVoice (Samsung's voice assistant) on Android M(6.0) and N(7.x) devices contains a vulnerability allowing arbitrary code execution through manipulation of dynamic libraries. This suggests insecure library loading that permits an attacker to inject or replace shared libraries to gain code execution with the application's privileges.

MitigationApply Samsung security updates released after September 2017 that address SVE-2017-9299. Users should avoid installing applications from untrusted sources and refrain from modifying system libraries.

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:= 6.0= 7.0= 7.1.0= 7.1.1= 7.1.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check the Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version is 6.0, 7.0, 7.1.0, 7.1.1, or 7.1.2
  2. Verify SVoice application is installed
    Check for SVoice in the app drawer, or run 'pm list packages | grep svoice' via ADB
    Affected if SVoice is present on the device
  3. Check if SVoice loads libraries from world-writable directories
    Run 'ps -ef | grep svoice' to find the process, then monitor library loading with 'strace -f -p <pid> open' during app use, looking for dlopen calls to paths like /data/local/tmp or /sdcard
    Affected if The app loads libraries from directories accessible to other applications or users
  4. Inspect SVoice app permissions
    Run 'dumpsys package com.samsung.android.voicewakeup' via ADB to check the app's requested permissions
    Affected if The app has permission to write to external storage or execute code from storage locations

The device is affected if it runs Android 6.0 through 7.1.2 AND has SVoice installed, and particularly if the app loads dynamic libraries from insecure paths accessible to other applications.

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 Samsung security updates released after September 2017 that address SVE-2017-9299. Users should avoid installing applications from untrusted sources and refrain from modifying system libraries.

Recommended fix Moderate confidence

Android 8.0+ or October 2017 security patch level

  1. 1. Check your Samsung device's current Android version and security patch level in Settings > About phone > Software information
  2. 2. Verify if your device has received the October 2017 security patch or later by checking Settings > About phone > Software information > Security patch level
  3. 3. If the security patch level is earlier than October 2017, check for system updates via Settings > System > Software update > Download updates manually
  4. 4. If no update is available from Samsung, consider upgrading to a device running Android 8.0 (Oreo) or later, which includes the patched SVoice implementation
  5. 5. As a temporary mitigation, disable SVoice app in Settings > Apps > SVoice > Disable
Caveat Upgrading to Android 8.0 may remove SVoice entirely (replaced with Bixby), and some legacy apps may be incompatible

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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