{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10139 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-10139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-10139 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."},"fix_prompt":"Check this codebase for CVE-2016-10139 and fix it if it is affected.\n\nWhat it is: CVE-2016-10139 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.\nExploitation: There is no known exploitation of CVE-2016-10139 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2016-10139/ (Markdown: https://insights.sbomify.com/CVE-2016-10139/index.md)","id":"CVE-2016-10139","markdown":"https://insights.sbomify.com/CVE-2016-10139/index.md","name":"CVE-2016-10139","record":{"aliases":["GHSA-q5ww-49gf-gp58"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BLU R1 HD Adups software","requires_auth":"low_privilege","summary":"Adups software on BLU devices exfiltrates user PII like call logs and texts to remote servers without consent.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"adups_fota","vendor":"adups"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"An issue was discovered on BLU R1 HD devices with Shanghai Adups software. The two package names involved in the exfiltration are com.adups.fota and com.adups.fota.sysoper. 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. Therefore, the app executing as the system user has been granted a number of powerful permissions even though they are not present in the com.adups.fota.sysoper app's AndroidManifest.xml file. This app provides the com.adups.fota app access to the user's call log, text messages, and various device identifiers through the com.adups.fota.sysoper.provider.InfoProvider component. The com.adups.fota app uses timestamps when it runs and is eligible to exfiltrate the user's PII every 72 hours. If 72 hours have passed since the value of the timestamp, then the exfiltration will be triggered by the user plugging in the device to charge or when they leave or enter a wireless network. The exfiltration occurs in the background without any user interaction.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2016-10139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-10140"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2016-10138"},"products":["n/a"],"published":"2017-01-13","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2016-10136","kev_date_added":null,"published":"2017-01-13"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2016-10137","kev_date_added":null,"published":"2017-01-13"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2016-10138","kev_date_added":null,"published":"2017-01-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Adups software on BLU devices exfiltrates user PII like call logs and texts to remote servers without consent.","url":"https://insights.sbomify.com/CVE-2016-10139/"}