FKIE_CVE-2017-5948

Vulnerability from fkie_nvd - Published: 2017-05-11 18:29 - Updated: 2025-04-20 01:37
Severity ?
5.9 (Medium) - CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Summary
An issue was discovered on OnePlus One, X, 2, 3, and 3T devices. OxygenOS and HydrogenOS are vulnerable to downgrade attacks. This is due to a lenient 'updater-script' in OTAs that does not check that the current version is lower than or equal to the given image's. Downgrades can occur even on locked bootloaders and without triggering a factory reset, allowing for exploitation of now-patched vulnerabilities with access to user data. This vulnerability can be exploited by a Man-in-the-Middle (MiTM) attacker targeting the update process. This is possible because the update transaction does not occur over TLS (CVE-2016-10370). In addition, a physical attacker can reboot the phone into recovery, and then use 'adb sideload' to push the OTA (on OnePlus 3/3T 'Secure Start-up' must be off).
References
cve@mitre.orghttps://alephsecurity.com/vulns/aleph-2017008Exploit, Technical Description, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://alephsecurity.com/vulns/aleph-2017008Exploit, Technical Description, Third Party Advisory
Impacted products
Vendor Product Version
oneplus oxygenos *
oneplus oneplus_2 -
oneplus oneplus_3 -
oneplus oneplus_3t -
oneplus oneplus_one -
oneplus oneplus_x -
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:oneplus:oxygenos:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "8189780A-EA20-4B96-A625-48D12948B3F2",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        },
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:h:oneplus:oneplus_2:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "332B048C-6522-41A7-9DAB-834FBFCA3C00",
              "vulnerable": false
            },
            {
              "criteria": "cpe:2.3:h:oneplus:oneplus_3:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "E6B1891E-38B0-42C5-89D3-3DC12217F087",
              "vulnerable": false
            },
            {
              "criteria": "cpe:2.3:h:oneplus:oneplus_3t:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "4C7E02CB-9EAC-4BFD-8CCC-337610E1CCEE",
              "vulnerable": false
            },
            {
              "criteria": "cpe:2.3:h:oneplus:oneplus_one:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "8B8AD37A-7539-4F16-8AC2-2556035B0DE2",
              "vulnerable": false
            },
            {
              "criteria": "cpe:2.3:h:oneplus:oneplus_x:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "C0A390FA-9B56-4645-991D-5E9CB16966B9",
              "vulnerable": false
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ],
      "operator": "AND"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "An issue was discovered on OnePlus One, X, 2, 3, and 3T devices. OxygenOS and HydrogenOS are vulnerable to downgrade attacks. This is due to a lenient \u0027updater-script\u0027 in OTAs that does not check that the current version is lower than or equal to the given image\u0027s. Downgrades can occur even on locked bootloaders and without triggering a factory reset, allowing for exploitation of now-patched vulnerabilities with access to user data. This vulnerability can be exploited by a Man-in-the-Middle (MiTM) attacker targeting the update process. This is possible because the update transaction does not occur over TLS (CVE-2016-10370). In addition, a physical attacker can reboot the phone into recovery, and then use \u0027adb sideload\u0027 to push the OTA (on OnePlus 3/3T \u0027Secure Start-up\u0027 must be off)."
    },
    {
      "lang": "es",
      "value": "Se detect\u00f3 un problema en los dispositivos OnePlus versiones One, X, 2, 3 y 3T. OxygenOS e HydrogenOS son vulnerables a ataques de degradaci\u00f3n. Esto se debe a un \"updater-script\" indulgente en OTAs que no comprueba que la versi\u00f3n actual sea inferior o igual a la de la imagen en cuesti\u00f3n. Las degradaciones pueden ocurrir incluso en cargadores de arranque bloqueados y sin activar un restablecimiento de f\u00e1brica, permitiendo la explotaci\u00f3n de las vulnerabilidades ahora parcheadas con acceso a los datos del usuario. Esta vulnerabilidad puede ser explotada por un atacante de tipo Man-in-the-Middle (MiTM) que se dirija al proceso de actualizaci\u00f3n. Esto es posible porque la transacci\u00f3n de actualizaci\u00f3n no se realiza por medio de TLS (CVE-2016-10370). Adicionalmente, un atacante f\u00edsico puede reiniciar el tel\u00e9fono en la recuperaci\u00f3n y luego usar \"adb sideload\" para empujar la OTA (en OnePlus 3/3T \"Secure Start-up\" debe estar desactivado)."
    }
  ],
  "id": "CVE-2017-5948",
  "lastModified": "2025-04-20T01:37:25.860",
  "metrics": {
    "cvssMetricV2": [
      {
        "acInsufInfo": false,
        "baseSeverity": "MEDIUM",
        "cvssData": {
          "accessComplexity": "MEDIUM",
          "accessVector": "NETWORK",
          "authentication": "NONE",
          "availabilityImpact": "NONE",
          "baseScore": 4.3,
          "confidentialityImpact": "NONE",
          "integrityImpact": "PARTIAL",
          "vectorString": "AV:N/AC:M/Au:N/C:N/I:P/A:N",
          "version": "2.0"
        },
        "exploitabilityScore": 8.6,
        "impactScore": 2.9,
        "obtainAllPrivilege": false,
        "obtainOtherPrivilege": false,
        "obtainUserPrivilege": false,
        "source": "nvd@nist.gov",
        "type": "Primary",
        "userInteractionRequired": false
      }
    ],
    "cvssMetricV30": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.9,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "version": "3.0"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 3.6,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2017-05-11T18:29:00.220",
  "references": [
    {
      "source": "cve@mitre.org",
      "tags": [
        "Exploit",
        "Technical Description",
        "Third Party Advisory"
      ],
      "url": "https://alephsecurity.com/vulns/aleph-2017008"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Exploit",
        "Technical Description",
        "Third Party Advisory"
      ],
      "url": "https://alephsecurity.com/vulns/aleph-2017008"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.