CVE-2025-0302
📋 TL;DR
An integer overflow vulnerability in OpenHarmony v4.1.2 and earlier allows local attackers to cause denial of service (DoS) by triggering system crashes or instability. This affects systems running vulnerable OpenHarmony versions where an attacker has local access.
💻 Affected Systems
- OpenHarmony
📦 What is this software?
Openharmony by Openatom
⚠️ Risk & Real-World Impact
Worst Case
Complete system crash or instability requiring reboot, potentially disrupting device functionality and availability.
Likely Case
Application or service crashes affecting specific functionality without complete system failure.
If Mitigated
Minimal impact with proper access controls limiting local attacker privileges.
🎯 Exploit Status
Requires local access and specific conditions to trigger the integer overflow. No public exploit code identified.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: OpenHarmony v4.1.3 or later
Vendor Advisory: https://gitee.com/openharmony/security/blob/master/zh/security-disclosure/2025/2025-02.md
Restart Required: Yes
Instructions:
1. Check current OpenHarmony version. 2. Update to v4.1.3 or later via official channels. 3. Reboot system after update. 4. Verify update completed successfully.
🔧 Temporary Workarounds
Restrict local access
allLimit local user privileges and access to vulnerable systems
# Implement least privilege principles for local users
# Review and restrict local account permissions
🧯 If You Can't Patch
- Implement strict access controls to limit local user privileges
- Monitor systems for abnormal crashes or instability and isolate affected devices
🔍 How to Verify
Check if Vulnerable:
Check OpenHarmony version: 'getprop ro.build.version.ohos' or equivalent system commandCheck Version:
getprop ro.build.version.ohosVerify Fix Applied:
Verify version is v4.1.3 or later and test system stability📡 Detection & Monitoring
Log Indicators:
- System crash logs
- Kernel panic messages
- Application/service abnormal termination
Network Indicators:
- None - local vulnerability only
SIEM Query:
Search for: 'system crash', 'kernel panic', 'segmentation fault' in system logs