Local information disclosure to malicious applications
Published Mar 12, 2020 · Updated Aug 4, 2024
Improper authentication in Huawei Honor V30 firmware before OxfordS-AN00A 10.0.1.167(C00E166R4P1) allows attackers to disclose information. The firmware improperly authenticates a target component during a device operation, but Huawei has not identified the component, operation, or information exposed. Exploitation requires loading a malicious application and user interaction; the published impact is limited to information disclosure.
Summary
What happened
Improper authentication in Huawei Honor V30 firmware before OxfordS-AN00A 10.0.1.167(C00E166R4P1) allows attackers to disclose information. The firmware improperly authenticates a target component during a device operation, but Huawei has not identified the component, operation, or information exposed. Exploitation requires loading a malicious application and user interaction; the published impact is limited to information disclosure.
The record
- CVE
- CVE-2020-9064
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- Honor V30
- Classifications
- CWE-287
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 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 OxfordS-AN00A 10.0.1.167(C00E166R4P1)
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