Local controller hang via repeated RPC calls
Published Apr 30, 2020 · Updated Aug 4, 2024
Resource-management error in ZTE ZENIC ONE R22b allows local users to hang the controller through repeated RPC calls. ZTE has not disclosed the affected RPC handler or the precise resource operation; it reports prolonged nonresponse and memory-overflow risk when other applications call RPC frequently during mass traffic. Low-privilege local access and mass traffic are required, and the affected releases are V16.19.10P02SP002 and V16.19.10P02SP005.
Summary
What happened
Resource-management error in ZTE ZENIC ONE R22b allows local users to hang the controller through repeated RPC calls. ZTE has not disclosed the affected RPC handler or the precise resource operation; it reports prolonged nonresponse and memory-overflow risk when other applications call RPC frequently during mass traffic. Low-privilege local access and mass traffic are required, and the affected releases are V16.19.10P02SP002 and V16.19.10P02SP005.
The record
- CVE
- CVE-2020-6867
- Published
- Apr 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- ZTE Corporation
- Product
- ZENIC ONE R22
- Classifications
- CWE-119, T1499.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 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=V16.19.10P02SP002
- Affected versionversion=V16.19.10P02SP005
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