dbcve.org
AndroidOperating system · Google

CVE-2016-11025

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 software through 2016-09-13 (Exynos AP chipsets). There is a memcpy heap-based buffer overflow in the OTP service. The Samsung ID is SVE-2016-7114 (December 2016).

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

A heap-based buffer overflow vulnerability exists in the OTP (One-Time Password) service on Samsung mobile devices using Exynos AP chipsets. The vulnerability is caused by an insecure memcpy operation that does not properly validate buffer sizes before copying data to the heap, potentially allowing remote attackers to execute arbitrary code.

MitigationApply vendor-supplied firmware updates from Samsung to patched software versions released after December 2016. There are no known workarounds; affected devices must be updated.

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:all versions

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. Confirm device is a Samsung mobile device
    Check the device manufacturer and model by viewing 'About phone' in Settings or running 'getprop ro.product.manufacturer' and 'getprop ro.product.model' via ADB
    Affected if Manufacturer is not Samsung or model is not a mobile device
  2. Verify the device uses an Exynos AP chipset
    Check the processor/chipset information in Settings > About phone > CPU or run 'getprop ro.hardware' or 'cat /proc/cpuinfo' via ADB to identify the chipset
    Affected if Chipset is not an Exynos variant (e.g., Snapdragon or other non-Exynos processors)
  3. Confirm the OTP service is present and accessible
    Check if the OTP service binary or daemon exists on the device. Look for '/system/bin/otp' or similar OTP-related services in /system/bin/ or via 'ps -A | grep -i otp' via ADB
    Affected if No OTP service or daemon is found on the device
  4. Determine if the Android version falls within the affected window
    Check the Android version in Settings > About phone > Android version or run 'getprop ro.build.version.sdk' via ADB
    Affected if Device runs any Android version (summary indicates all versions are affected) and meets the Samsung Exynos criteria

The device is affected if it is a Samsung mobile device with an Exynos chipset that has the OTP service present, regardless of Android version since all versions are impacted.

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 vendor-supplied firmware updates from Samsung to patched software versions released after December 2016. There are no known workarounds; affected devices must be updated.

Recommended fix Moderate confidence

Samsung December 2016 Security Update (SVE-2016-7114) or later monthly security patch

  1. 1. Navigate to Settings on the Samsung device
  2. 2. Go to 'About phone' or 'About device'
  3. 3. Tap on 'Software update' or 'Security patch level'
  4. 4. Ensure the device has received the December 2016 security update or later (Security Patch Level: 2016-12-01 or newer)
  5. 5. If an update is available, download and install it
  6. 6. Verify the security patch level has been updated in Settings > About phone > Software information > Security patch level

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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