Local availability failure via IPC deserialization
Published Jun 6, 2025 · Updated Jun 9, 2025
Deserialization in the IPC module in Huawei HarmonyOS 5.0.0 allows local users to cause an unspecified availability failure. The CWE-248 mapping establishes that deserialization can raise an exception that the IPC module does not catch, although Huawei has not identified the parser or message type. Local access is required, but no privileges or user interaction are required; Huawei does not specify whether exploitation causes a hang, crash, reboot, or broader service interruption.
Summary
What happened
Deserialization in the IPC module in Huawei HarmonyOS 5.0.0 allows local users to cause an unspecified availability failure. The CWE-248 mapping establishes that deserialization can raise an exception that the IPC module does not catch, although Huawei has not identified the parser or message type. Local access is required, but no privileges or user interaction are required; Huawei does not specify whether exploitation causes a hang, crash, reboot, or broader service interruption.
The record
- CVE
- CVE-2025-48907
- Published
- Jun 6, 2025
- Updated
- Jun 9, 2025
- Vendor
- MindSpore
- Product
- HarmonyOS
- Classifications
- CWE-248, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 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=5.0.0
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