{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8851 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8851 is a medium-severity vulnerability in n/a, published on 11 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8851 and fix it if it is affected.\n\nWhat it is: CVE-2017-8851 is a medium-severity vulnerability in n/a, published on 11 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-8851 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-2017-8851/ (Markdown: https://insights.sbomify.com/CVE-2017-8851/index.md)","id":"CVE-2017-8851","markdown":"https://insights.sbomify.com/CVE-2017-8851/index.md","name":"CVE-2017-8851","record":{"aliases":["GHSA-4c45-vj44-g553"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OnePlus OTA updater","requires_auth":"none","summary":"Attackers can bypass OTA verification to install incorrect firmware on OnePlus devices, potentially causing denial of service or enabling further exploitation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oxygenos","vendor":"oneplus"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"An issue was discovered on OnePlus One and X devices. Due to a lenient updater-script on the OnePlus One and X OTA images, the fact that both products use the same OTA verification keys, and the fact that both products share the same 'ro.build.product' system property, attackers can install OTAs of one product over the other, even on locked bootloaders. That could theoretically allow for exploitation of vulnerabilities patched on one image but not on the other, in addition to expansion of the attack surface. Moreover, the vulnerability may result in having the device unusable until a Factory Reset is performed. This vulnerability can be exploited by Man-in-the-Middle (MiTM) attackers targeting the update process. This is possible because the update transaction does not occur over TLS (CVE-2016-10370). In addition, physical attackers can reboot the phone into recovery, and then use 'adb sideload' to push the OTA.","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":"Security feature bypass in n/a","id":"CVE-2017-8851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-8852"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-8850"},"products":["n/a"],"published":"2017-05-11","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5624","kev_date_added":null,"published":"2017-03-12"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5626","kev_date_added":null,"published":"2017-03-12"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2017-5554","kev_date_added":null,"published":"2017-01-23"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2016-10370","kev_date_added":null,"published":"2017-05-11"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-5947","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":6.6,"headline":"Security feature bypass in n/a","id":"CVE-2017-5623","kev_date_added":null,"published":"2017-03-19"},{"cvss_score":5.9,"headline":"Security feature bypass in n/a","id":"CVE-2017-5948","kev_date_added":null,"published":"2017-05-11"}],"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-05","vendors":["n/a"]},"summary":"Attackers can bypass OTA verification to install incorrect firmware on OnePlus devices, potentially causing denial of service or enabling further exploitation.","url":"https://insights.sbomify.com/CVE-2017-8851/"}