dbcve.org
Adups FotaApplication · Adups

CVE-2016-10137

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 the user's sent and received text messages and call log. This allows a third-party app to obtain PII from the user without permission to do so.

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 pre-installed system app (com.adups.fota.sysoper) on BLU R1 HD devices contains a content provider (InfoProvider) that runs as the system user (android.uid.system) and is exported without proper access controls, allowing any installed application to read, write, and delete SMS messages and call logs without any permissions.

MitigationApply vendor firmware updates from BLU or Shanghai Adups that remove or secure the vulnerable content provider; if no update is available, remove the com.adups.fota.sysoper app via root access or replace the device.

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 com.adups.fota.sysoper app is installed
    Run 'pm list packages | grep com.adups.fota.sysoper' or check installed packages via device settings to see if com.adups.fota.sysoper exists on the device
    Affected if The package com.adups.fota.sysoper is present on the device
  2. Check if the InfoProvider content provider is exported
    Run 'dumpsys package com.adups.fota.sysoper' and look for the InfoProvider component with 'exported=true' in the content provider declarations
    Affected if The InfoProvider is exported and accessible to other applications
  3. Examine the app's manifest or run 'dumpsys package com.adups.fota.sysoper' to verify the sharedUserId is set to android.uid.system or the app has been granted system-level privileges
    Affected if The app runs with system-level privileges (android.uid.system)
  4. Verify SMS and call log access is possible without permissions
    Attempt to query the content provider URI (typically content://com.adups.fota.sysoper.info.provider or similar path within that package) from a non-privileged app to read SMS or call logs
    Affected if SMS messages or call logs can be read, written, or deleted without the app holding READ_SMS, WRITE_SMS, or READ_CALL_LOG permissions

If the com.adups.fota.sysoper package is installed and its InfoProvider content provider is exported, any application on the device can access SMS and call logs without any permissions, indicating the device is affected by CVE-2016-10137.

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

Apply vendor firmware updates from BLU or Shanghai Adups that remove or secure the vulnerable content provider; if no update is available, remove the com.adups.fota.sysoper app via root access or replace the device.

Fix this in Adups Fota 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-2016-10137 — 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-10137 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