LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10370: An issue was discovered on OnePlus devices such as the 3T.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Some OnePlus phones, including the 3T, received OTA update images over unencrypted HTTP. The updates were still digitally signed, so this alone is not evidence of arbitrary firmware installation. The business concern is added attack surface: a network attacker could interfere with update delivery and potentially combine it with other OnePlus updater vulnerabilities. Exposure is most likely in legacy OnePlus fleets or BYOD devices using affected OTA updater behavior, especially OnePlus 3T-class devices. The source bundle does not provide complete affected version ranges, CPEs, or confirmed fixed builds. Prioritize if legacy OnePlus devices can access corporate data or trusted networks. The issue is not reported as actively exploited here, but it weakens update security and can amplify other vulnerabilities. Unsupported devices should be restricted or removed. Mitigation focus: Check OnePlus guidance and firmware notes for fixed OTA updater behavior.; Update affected devices to a vendor-supported firmware build where available.; Retire or restrict unsupported legacy OnePlus devices from sensitive access..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-10370 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.