Physical authentication bypass via weak credentials
Published Feb 18, 2020 · Updated Aug 4, 2024
Insufficient authentication in Huawei OSCA-550 series firmware 1.0.1.21(SP3) allows physically proximate attackers to perform restricted operations. The credential-checking locus and affected operations are undisclosed; Huawei states only that the software accepts a weak credential where a strong one is required. Physical access to the device is required, and the reported consequence is limited to bypassing authentication for unspecified operations.
Summary
What happened
Insufficient authentication in Huawei OSCA-550 series firmware 1.0.1.21(SP3) allows physically proximate attackers to perform restricted operations. The credential-checking locus and affected operations are undisclosed; Huawei states only that the software accepts a weak credential where a strong one is required. Physical access to the device is required, and the reported consequence is limited to bypassing authentication for unspecified operations.
The record
- CVE
- CVE-2020-1789
- Published
- Feb 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1078
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 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?
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
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