CVE-2017-8851: Medium severity oxygenos vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-8851?
CVE-2017-8851 has a medium severity rating due to the potential for unauthorized installation of OTA updates.
How do I fix CVE-2017-8851?
To fix CVE-2017-8851, ensure that you update to the latest firmware version provided by OnePlus that addresses this vulnerability.
What devices are affected by CVE-2017-8851?
CVE-2017-8851 affects OnePlus One and OnePlus X devices that utilize the affected OTA update mechanism.
What type of vulnerability is CVE-2017-8851?
CVE-2017-8851 is an OTA update verification vulnerability that allows for the installation of unauthorized updates.
Can CVE-2017-8851 be exploited remotely?
Yes, CVE-2017-8851 can be exploited remotely by an attacker to install malicious OTA updates on affected devices.