Arbitrary code execution via out-of-bounds write
Published Jul 2, 2024 · Updated Aug 2, 2024
Out-of-bounds write in OpenHarmony 4.0.0 through 4.0.1 allows remote authenticated users to execute code in pre-installed apps. The Arkcompiler ETS Runtime writes beyond an allocated buffer, but OpenHarmony has not disclosed the affected function, input field, or request path. The vendor assessment requires adjacent-network access and low privileges, and successful exploitation crosses a security boundary to affect app confidentiality and integrity.
Summary
What happened
Out-of-bounds write in OpenHarmony 4.0.0 through 4.0.1 allows remote authenticated users to execute code in pre-installed apps. The Arkcompiler ETS Runtime writes beyond an allocated buffer, but OpenHarmony has not disclosed the affected function, input field, or request path. The vendor assessment requires adjacent-network access and low privileges, and successful exploitation crosses a security boundary to affect app confidentiality and integrity.
The record
- CVE
- CVE-2024-36260
- Published
- Jul 2, 2024
- Updated
- Aug 2, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-787
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.0.0 <=4.0.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