# CVE-2017-5622: Auth bypass in n/a

> A physical attacker can connect a malicious charger to a powered-off OnePlus device to enable ADB without authorization, allowing data exfiltration or further exploitation.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pwjc-cjmg-4g8f

## What is CVE-2017-5622?

CVE-2017-5622 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

With OxygenOS before 4.0.3, when a charger is connected to a powered-off OnePlus 3 or 3T device, the platform starts with adbd enabled. Therefore, a malicious charger or a physical attacker can open up, without authorization, an ADB session with the device, in order to further exploit other vulnerabilities and/or exfiltrate sensitive information.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Oneplus Oxygenos.

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

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

## Is CVE-2017-5622 being exploited?

There is no known exploitation of CVE-2017-5622 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-5626](https://insights.sbomify.com/CVE-2017-5626/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5622 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5622 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-5622/ (Markdown: https://insights.sbomify.com/CVE-2017-5622/index.md)
```

## Sources

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

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