Menu

Star on GitHub · 3.2k

CVE-2016-10370

7.5 · HIGH

An issue was discovered on OnePlus devices such as the 3T.

Published May 11, 2017CWE-284EPSS 1.15%

Overview

CVE-2016-10370 is a high-severity vulnerability. It was published on May 11, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

An issue was discovered on OnePlus devices such as the 3T. The OnePlus OTA Updater pushes the signed-OTA image over HTTP without TLS. While it does not allow for installation of arbitrary OTAs (due to the digital signature), it unnecessarily increases the attack surface, and allows for remote exploitation of other vulnerabilities such as CVE-2017-5948, CVE-2017-8850, and CVE-2017-8851.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-10370?

CVE-2016-10370 is a high-severity vulnerability. It was published on May 11, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).

How severe is CVE-2016-10370?

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-10370?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-10370?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-10370 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2016

View all