Service disruption via double-free memory release
Published Mar 20, 2020 · Updated Aug 4, 2024
Double-free memory corruption in Huawei CampusInsight V100R019C00 and ManageOne 6.5.RC2.B050 allows local users to interrupt a service. Huawei has not published the affected component or the operations that release the same memory allocation twice. Exploitation requires low-privilege local access to an affected product and causes only an unspecified service abnormality.
Summary
What happened
Double-free memory corruption in Huawei CampusInsight V100R019C00 and ManageOne 6.5.RC2.B050 allows local users to interrupt a service. Huawei has not published the affected component or the operations that release the same memory allocation twice. Exploitation requires low-privilege local access to an affected product and causes only an unspecified service abnormality.
The record
- CVE
- CVE-2020-1862
- Published
- Mar 20, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 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.
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