Vulnerability-Lookup

CNVD-2017-10578

Vulnerability from cnvd - Published: 2017-06-21

Title

OnePlus X和One设备安全绕过漏洞

Description

OnePlusX和One都是中国一加科技（OnePlus）公司的智能手机。OxygenOS和HydrogenOS都是其自带的操作系统。 OnePlusX和One存在安全绕过漏洞。攻击者可利用此漏洞通过执行中间人攻击绕过某些安全限制并执行未授权的操作，发起进一步攻击。

Severity

中

Patch Name

OnePlus X和One设备安全绕过漏洞的补丁

Patch Description

OnePlusX和One都是中国一加科技（OnePlus）公司的智能手机。OxygenOS和HydrogenOS都是其自带的操作系统。 OnePlusX和One存在安全绕过漏洞。攻击者可利用此漏洞通过执行中间人攻击绕过某些安全限制并执行未授权的操作，发起进一步攻击。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

用户可参考如下厂商提供的安全补丁以修复该漏洞： https://alephsecurity.com/vulns/aleph-2017021

Reference

http://www.securityfocus.com/bid/98501 https://nvd.nist.gov/vuln/detail/CVE-2017-8851

Impacted products

Name
['OnePlus OnePlus One', 'OnePlus OnePlus X']

Show details on source website

JSON

To clipboard

{
  "bids": {
    "bid": {
      "bidNumber": "98501"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-8851",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8851"
    }
  },
  "description": "OnePlusX\u548cOne\u90fd\u662f\u4e2d\u56fd\u4e00\u52a0\u79d1\u6280\uff08OnePlus\uff09\u516c\u53f8\u7684\u667a\u80fd\u624b\u673a\u3002OxygenOS\u548cHydrogenOS\u90fd\u662f\u5176\u81ea\u5e26\u7684\u64cd\u4f5c\u7cfb\u7edf\u3002\r\n\r\nOnePlusX\u548cOne\u5b58\u5728\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u6b64\u6f0f\u6d1e\u901a\u8fc7\u6267\u884c\u4e2d\u95f4\u4eba\u653b\u51fb\u7ed5\u8fc7\u67d0\u4e9b\u5b89\u5168\u9650\u5236\u5e76\u6267\u884c\u672a\u6388\u6743\u7684\u64cd\u4f5c\uff0c\u53d1\u8d77\u8fdb\u4e00\u6b65\u653b\u51fb\u3002",
  "discovererName": "Roee Hay of Aleph Research, HCL Technologies",
  "formalWay": "\u7528\u6237\u53ef\u53c2\u8003\u5982\u4e0b\u5382\u5546\u63d0\u4f9b\u7684\u5b89\u5168\u8865\u4e01\u4ee5\u4fee\u590d\u8be5\u6f0f\u6d1e\uff1a\r\nhttps://alephsecurity.com/vulns/aleph-2017021",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-10578",
  "openTime": "2017-06-21",
  "patchDescription": "OnePlusX\u548cOne\u90fd\u662f\u4e2d\u56fd\u4e00\u52a0\u79d1\u6280\uff08OnePlus\uff09\u516c\u53f8\u7684\u667a\u80fd\u624b\u673a\u3002OxygenOS\u548cHydrogenOS\u90fd\u662f\u5176\u81ea\u5e26\u7684\u64cd\u4f5c\u7cfb\u7edf\u3002\r\n\r\nOnePlusX\u548cOne\u5b58\u5728\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u6b64\u6f0f\u6d1e\u901a\u8fc7\u6267\u884c\u4e2d\u95f4\u4eba\u653b\u51fb\u7ed5\u8fc7\u67d0\u4e9b\u5b89\u5168\u9650\u5236\u5e76\u6267\u884c\u672a\u6388\u6743\u7684\u64cd\u4f5c\uff0c\u53d1\u8d77\u8fdb\u4e00\u6b65\u653b\u51fb\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "OnePlus X\u548cOne\u8bbe\u5907\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "OnePlus OnePlus One",
      "OnePlus OnePlus X"
    ]
  },
  "referenceLink": "http://www.securityfocus.com/bid/98501\r\nhttps://nvd.nist.gov/vuln/detail/CVE-2017-8851",
  "serverity": "\u4e2d",
  "submitTime": "2017-05-24",
  "title": "OnePlus X\u548cOne\u8bbe\u5907\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e"
}

CVE-2017-8851 (GCVE-0-2017-8851)

Vulnerability from cvelistv5 – Published: 2017-05-11 18:00 – Updated: 2024-08-05 16:48

Summary

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.

Severity

No CVSS data available.

CWE

Assigner

mitre CNA under the mitre root

CNA scorecard E 29/100 over 2354 records in the last 180 days details

References

1 reference

URL	Tags
https://alephsecurity.com/vulns/aleph-2017021	x_refsource_MISC

Date Public

2017-05-11 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T16:48:22.645Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://alephsecurity.com/vulns/aleph-2017021"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2017-05-11T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "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 \u0027ro.build.product\u0027 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 \u0027adb sideload\u0027 to push the OTA."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-05-11T17:57:01.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://alephsecurity.com/vulns/aleph-2017021"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2017-8851",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "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 \u0027ro.build.product\u0027 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 \u0027adb sideload\u0027 to push the OTA."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://alephsecurity.com/vulns/aleph-2017021",
              "refsource": "MISC",
              "url": "https://alephsecurity.com/vulns/aleph-2017021"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2017-8851",
    "datePublished": "2017-05-11T18:00:00.000Z",
    "dateReserved": "2017-05-08T00:00:00.000Z",
    "dateUpdated": "2024-08-05T16:48:22.645Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted