Root shell via unauthenticated UART boot interruption
Published Jan 18, 2023 · Updated Jul 5, 2026
Missing authorization in OKER G955V1 firmware 1.03.02.20161128 allows physically proximate attackers to obtain a root shell. Pressing q and Enter through the exposed 115200-baud UART during boot stops initialization and opens an unauthenticated root shell. Physical access to the internal circuit board and a serial adapter are required; successful access permits arbitrary root commands, data reads, configuration changes, and service interruption.
Summary
What happened
Missing authorization in OKER G955V1 firmware 1.03.02.20161128 allows physically proximate attackers to obtain a root shell. Pressing q and Enter through the exposed 115200-baud UART during boot stops initialization and opens an unauthenticated root shell. Physical access to the internal circuit board and a serial adapter are required; successful access permits arbitrary root commands, data reads, configuration changes, and service interruption.
The record
- CVE
- CVE-2020-22007
- Published
- Jan 18, 2023
- Updated
- Jul 5, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2023CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OKER_UART_2 demonstration videoproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo