dbcve.org
Adups FotaApplication · Adups

CVE-2016-10136

HIGH · 7.8 CVSS v3.0 Published 2017-01-13
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
An issue was discovered on BLU R1 HD devices with Shanghai Adups software. The content provider named com.adups.fota.sysoper.provider.InfoProvider in the app with a package name of com.adups.fota.sysoper allows any app on the device to read, write, and delete files as the system user. In the com.adups.fota.sysoper app's AndroidManifest.xml file, it sets the android:sharedUserId attribute to a value of android.uid.system which makes it execute as the system user, which is a very privileged user on the device. This allows a third-party app to read, write, and delete files owned by the system user. The third-party app can modify the /data/system/users/0/settings_secure.xml file to add an app as a notification listener to be able to receive the text of notifications as they are received on the device. This also allows the /data/system/users/0/accounts.db to be read which contains authentication tokens for various accounts on the device. The third-party app can obtain privileged information and also modify files to obtain more privileges on the device.

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 content provider in the pre-installed com.adups.fota.sysoper app runs with system user privileges (android.uid.system) and is exported without proper access controls, allowing any installed app to read, write, and delete system files. Attackers can modify settings_secure.xml to add notification listeners and read accounts.db to steal authentication tokens.

MitigationThis is a firmware-level vulnerability requiring a patch from the device manufacturer (BLU) and/or Shanghai Adups. Users of affected devices should consider replacing the device or seeking manufacturer-provided security updates. Implementing network segmentation and monitoring for anomalous account access can serve as compensating controls.

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

CVSS:3.0/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 if the vulnerable app is installed
    Check if com.adups.fota.sysoper exists on the device by listing installed packages using 'pm list packages' or checking /data/data/ for the app directory
    Affected if The com.adups.fota.sysoper package is present on the device
  2. Confirm the content provider is exported
    Examine the app's AndroidManifest.xml for a content provider with android:exported="true" and no proper android:permission constraints, or use drozer to test if the provider accepts queries from other apps
    Affected if The content provider in com.adups.fota.sysoper is exported without android:writePermission or android:readPermission restrictions
  3. Verify system user privileges
    Check if the app runs with android.uid.system by examining the app's UID in /data/system/packages.xml or using 'dumpsys package' to view the app's declared uid
    Affected if The app declares android:sharedUserId="android.uid.system" or runs with UID 1000 (system)
  4. Inspect settings_secure.xml for unauthorized listeners
    Read /data/system/users/0/settings_secure.xml or use 'settings get secure' commands to check for notification listener entries such as 'enabled_notification_listeners' that were not explicitly authorized
    Affected if The settings_secure.xml file contains notification listener entries that were not added by the device owner or contain unexpected package names

A device is affected if it has the com.adups.fota.sysoper app with an exported content provider running with system privileges, allowing any app to modify settings_secure.xml or access accounts.db.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is a firmware-level vulnerability requiring a patch from the device manufacturer (BLU) and/or Shanghai Adups. Users of affected devices should consider replacing the device or seeking manufacturer-provided security updates. Implementing network segmentation and monitoring for anomalous account access can serve as compensating controls.

Fix this in Adups Fota Scoped from the published advisory
  • Consultation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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