Memory disclosure and corruption via out-of-bounds access
Published Oct 14, 2022 · Updated May 14, 2025
Out-of-bounds access in OpenHarmony 3.1.2 and earlier and 3.0.6 and earlier allows local users to disclose or corrupt memory. The /dev/mmz_userdev driver reads beyond a memory boundary for unprivileged callers and writes beyond it for processes running with the system UID. Any local unprivileged process can expose sensitive memory; out-of-bounds writes require the system UID and cause unspecified memory corruption.
Summary
What happened
Out-of-bounds access in OpenHarmony 3.1.2 and earlier and 3.0.6 and earlier allows local users to disclose or corrupt memory. The /dev/mmz_userdev driver reads beyond a memory boundary for unprivileged callers and writes beyond it for processes running with the system UID. Any local unprivileged process can expose sensitive memory; out-of-bounds writes require the system UID and cause unspecified memory corruption.
The record
- CVE
- CVE-2022-41686
- Published
- Oct 14, 2022
- Updated
- May 14, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-787, CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 14, 2025Record 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=OpenHarmony-v3.0.x-LTS <=3.0.6
- Affected versionversion=OpenHarmony-v3.1.x-Release <=3.1.2
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.
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