Root command execution via unauthenticated UART console
Published Jan 6, 2020 · Updated Aug 5, 2024
Improper access control in the UART console of OKER G232V1 1.03.02.20161129 allows physically proximate attackers to execute root commands. The console accepts commands with root privileges after an interrupted boot sequence without authenticating the attached operator. Physical device access and identification of the UART pins are required; exploitation grants root-level command execution, access to device data, and the ability to plant a backdoor.
Summary
What happened
Improper access control in the UART console of OKER G232V1 1.03.02.20161129 allows physically proximate attackers to execute root commands. The console accepts commands with root privileges after an interrupted boot sequence without authenticating the attached operator. Physical device access and identification of the UART pins are required; exploitation grants root-level command execution, access to device data, and the ability to plant a backdoor.
The record
- CVE
- CVE-2019-20348
- Published
- Jan 6, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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.
Weakness, pattern, technique
Public exploit references
- OKER UART proof-of-concept videoproof of concept · unverified
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