Local information disclosure via kernel out-of-bounds read
Published Dec 3, 2024 · Updated Dec 3, 2024
Out-of-bounds read in OpenHarmony LiteOS-A 4.1.0 through 4.1.1 allows local users to disclose information from kernel memory. OpenHarmony identifies the affected locus only as the kernel_liteos_a module and has not published the faulty function, input path, or missing bounds operation. Low-privileged local access is required; no user interaction is needed, and the documented consequence is confidentiality loss without data modification or service interruption.
Summary
What happened
Out-of-bounds read in OpenHarmony LiteOS-A 4.1.0 through 4.1.1 allows local users to disclose information from kernel memory. OpenHarmony identifies the affected locus only as the kernel_liteos_a module and has not published the faulty function, input path, or missing bounds operation. Low-privileged local access is required; no user interaction is needed, and the documented consequence is confidentiality loss without data modification or service interruption.
The record
- CVE
- CVE-2024-9978
- Published
- Dec 3, 2024
- Updated
- Dec 3, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 3, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 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=v4.1.0 <=4.1.1
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