CVE-2017-5622
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWith 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOn OnePlus 3 and 3T devices running OxygenOS before 4.0.3, the Android Debug Bridge daemon (adbd) is automatically enabled when the device receives power while powered off, even without user authentication. This allows a malicious charger or physical attacker to establish an unauthorized ADB session to exploit further vulnerabilities or exfiltrate data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelRun 'getprop ro.product.model' or check the device settings under About Phone > Model Number. Verify it is OnePlus 3 or OnePlus 3T.Affected if Device is a OnePlus 3 or 3T model.
-
Check OxygenOS versionRun 'getprop ro.oxygen.version' or go to Settings > About Phone > OxygenOS version. Compare the version number to the affected range.Affected if OxygenOS version is 4.0.2 or earlier.
-
Verify ADB daemon state on power-onWith the device powered off, connect a trusted USB cable to a computer and observe if the device enumerates as an ADB device without any screen interaction or unlock. Use 'adb devices' on the connected host to check.Affected if Device appears as an ADB device immediately upon applying power without user unlock.
-
Check USB debugging statusGo to Settings > Developer Options > USB Debugging, or run 'getprop persist.sys.usb.config' to see the current USB configuration.Affected if USB debugging is enabled and the device allows ADB access without user authentication on boot.
A user is affected if they have a OnePlus 3 or 3T device running OxygenOS 4.0.2 or earlier, where the ADB daemon becomes accessible immediately upon power-on without user unlock.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate OxygenOS to version 4.0.3 or later, which prevents adbd from starting automatically on power-on without user unlock. Avoid connecting to untrusted chargers or use USB restricted mode where available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data