Application crashes via runtime type confusion
Published Jul 2, 2024 · Updated Aug 2, 2024
Type confusion in the ArkCompiler ETS Runtime in OpenHarmony 4.0.1 and earlier allows local users to crash applications. OpenHarmony has not disclosed the runtime object, code path, or incompatible access responsible for the type confusion. Low-privilege local access is required, and the documented consequence is limited to application crashes.
Summary
What happened
Type confusion in the ArkCompiler ETS Runtime in OpenHarmony 4.0.1 and earlier allows local users to crash applications. OpenHarmony has not disclosed the runtime object, code path, or incompatible access responsible for the type confusion. Low-privilege local access is required, and the documented consequence is limited to application crashes.
The record
- CVE
- CVE-2024-36278
- Published
- Jul 2, 2024
- Updated
- Aug 2, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-843, T1499
- Attack vector
- local
- 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=4.0 <4.0.1
- 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