Code execution via kernel-address rewriting
Published Aug 2, 2021 · Updated Aug 3, 2024
Permission-control failure in Huawei EMUI 11.0.0 allows attackers to execute code by rewriting a kernel address on affected phones. Huawei identifies the locus only as kernel-address rewriting and has not published the affected kernel component or the operation that permits the rewrite. Required access and privileges are undisclosed, so exposure cannot be narrowed beyond affected Huawei phones and code execution.
Summary
What happened
Permission-control failure in Huawei EMUI 11.0.0 allows attackers to execute code by rewriting a kernel address on affected phones. Huawei identifies the locus only as kernel-address rewriting and has not published the affected kernel component or the operation that permits the rewrite. Required access and privileges are undisclosed, so exposure cannot be narrowed beyond affected Huawei phones and code execution.
The record
- CVE
- CVE-2021-22389
- Published
- Aug 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- MindSpore
- Product
- EMUI
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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=11.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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