# CVE-2016-10136: Privilege escalation in n/a

> A third-party app can exploit a system-level content provider to read sensitive data and modify system files, gaining elevated privileges on BLU R1 HD devices.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j3w8-vm75-wjhh

## What is CVE-2016-10136?

CVE-2016-10136 is a high-severity vulnerability in n/a, published on 13 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-310

## Which versions are affected by CVE-2016-10136?

It affects 1 product.


Products: Adups Adups Fota.

## How do I fix CVE-2016-10136?

No fix has been published for CVE-2016-10136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-10136 being exploited?

There is no known exploitation of CVE-2016-10136 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-10137](https://insights.sbomify.com/CVE-2016-10137/): Missing authorization in n/a (high 7.8)
- [CVE-2016-10138](https://insights.sbomify.com/CVE-2016-10138/): Privilege escalation in n/a (high 7.8)
- [CVE-2016-10139](https://insights.sbomify.com/CVE-2016-10139/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10136 and fix it if it is affected.

What it is: CVE-2016-10136 is a high-severity vulnerability in n/a, published on 13 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10136 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-10136/ (Markdown: https://insights.sbomify.com/CVE-2016-10136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10136
- OSV: https://osv.dev/vulnerability/CVE-2016-10136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-10136/
Summaries are generated and may contain mistakes; the official description above is the record.