CVE-2024-37185

8.2 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary code in pre-installed applications on OpenHarmony devices through an out-of-bounds write. It affects OpenHarmony v4.0.0 and earlier versions. Attackers can potentially gain control over affected systems without user interaction.

💻 Affected Systems

Products:
  • OpenHarmony
Versions: v4.0.0 and prior versions
Operating Systems: OpenHarmony
Default Config Vulnerable: ⚠️ Yes
Notes: Affects pre-installed applications specifically; custom apps may not be vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing remote code execution with highest privileges, enabling data theft, persistence, and lateral movement.

🟠

Likely Case

Remote code execution in pre-installed app context, potentially leading to data exfiltration, surveillance, or further exploitation.

🟢

If Mitigated

Limited impact with proper network segmentation and minimal exposed services, though local network attacks remain possible.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Remote exploitation without authentication is indicated by the description, though specific exploit details are not publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: OpenHarmony v4.0.1 or later

Vendor Advisory: https://gitee.com/openharmony/security/blob/master/zh/security-disclosure/2024/2024-07.md

Restart Required: Yes

Instructions:

1. Check current OpenHarmony version. 2. Update to v4.0.1 or later via official channels. 3. Reboot device after update. 4. Verify update completion.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate OpenHarmony devices from untrusted networks and internet exposure.

Application Restrictions

all

Disable or restrict network access for non-essential pre-installed applications.

🧯 If You Can't Patch

  • Segment affected devices on isolated network segments with strict firewall rules.
  • Implement application allowlisting to prevent execution of unauthorized code.

🔍 How to Verify

Check if Vulnerable:

Check OpenHarmony version via system settings or command 'getprop ro.build.version.ohos' - if version is 4.0.0 or earlier, device is vulnerable.

Check Version:

getprop ro.build.version.ohos

Verify Fix Applied:

Verify version is 4.0.1 or later using same command and ensure no abnormal application behavior.

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from pre-installed apps
  • Memory access violations in system logs
  • Network connections from unexpected system processes

Network Indicators:

  • Unexpected outbound connections from OpenHarmony devices
  • Suspicious payloads targeting OpenHarmony services

SIEM Query:

source="openharmony" AND (event_type="memory_violation" OR process_name="*preinstalled*")

🔗 References

📤 Share & Export