# CVE-2017-5626: Security feature bypass in n/a

> Hidden fastboot commands allow attackers to bypass bootloader lock restrictions, enabling persistent root access and data theft on OnePlus devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4vmj-9vqv-5mj5

## What is CVE-2017-5626?

CVE-2017-5626 is a critical vulnerability in n/a, published on 12 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OxygenOS before version 4.0.2, on OnePlus 3 and 3T, has two hidden fastboot oem commands (4F500301 and 4F500302) that allow the attacker to lock/unlock the bootloader, disregarding the 'OEM Unlocking' checkbox, without user confirmation and without a factory reset. This allows for persistent code execution with high privileges (kernel/root) with complete access to user data.

## Which versions are affected by CVE-2017-5626?

It affects 1 product.


Products: Oneplus Oxygenos.

## How do I fix CVE-2017-5626?

No fix has been published for CVE-2017-5626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5626 being exploited?

There is no known exploitation of CVE-2017-5626 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-5624](https://insights.sbomify.com/CVE-2017-5624/): Security feature bypass in n/a (critical 9.8)
- [CVE-2017-5554](https://insights.sbomify.com/CVE-2017-5554/): Security feature bypass in n/a (high 8.1)
- [CVE-2016-10370](https://insights.sbomify.com/CVE-2016-10370/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-5947](https://insights.sbomify.com/CVE-2017-5947/): Security feature bypass in n/a (medium 6.8)
- [CVE-2017-5623](https://insights.sbomify.com/CVE-2017-5623/): Security feature bypass in n/a (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5626 and fix it if it is affected.

What it is: CVE-2017-5626 is a critical vulnerability in n/a, published on 12 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5626 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5626/ (Markdown: https://insights.sbomify.com/CVE-2017-5626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5626
- OSV: https://osv.dev/vulnerability/CVE-2017-5626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5626/
Summaries are generated and may contain mistakes; the official description above is the record.