Clock-information disclosure via pre-unlock logic error
Published May 29, 2020 · Updated Aug 4, 2024
Improper authentication in Huawei Honor 9X firmware before 9.1.1.172(C00E170R8P1) allows physically proximate attackers to read clock information. The clock function contains a logic error that processes a rapid sequence of crafted pre-unlock operations without enforcing the normal unlock boundary. Physical possession of a locked phone is required, and the demonstrated consequence is limited to disclosure of clock information.
Summary
What happened
Improper authentication in Huawei Honor 9X firmware before 9.1.1.172(C00E170R8P1) allows physically proximate attackers to read clock information. The clock function contains a logic error that processes a rapid sequence of crafted pre-unlock operations without enforcing the normal unlock boundary. Physical possession of a locked phone is required, and the demonstrated consequence is limited to disclosure of clock information.
The record
- CVE
- CVE-2020-1833
- Published
- May 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Huawei
- Product
- Honor 9X
- Classifications
- CWE-287
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Versions earlier than 9.1.1.172(C00E170R8P1)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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