CVE-2024-37030

8.2 HIGH

📋 TL;DR

CVE-2024-37030 is a use-after-free vulnerability in OpenHarmony v4.0.0 and earlier that allows remote attackers to execute arbitrary code in pre-installed applications. This affects devices running vulnerable OpenHarmony versions, potentially enabling complete system compromise through malicious network interactions.

💻 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. All devices running affected OpenHarmony versions are impacted.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote attacker gains full control of affected device, installs persistent malware, accesses sensitive data, and pivots to other network resources.

🟠

Likely Case

Attackers exploit pre-installed apps to execute malicious code, potentially stealing user data, installing backdoors, or disrupting device functionality.

🟢

If Mitigated

With proper network segmentation and application sandboxing, impact limited to isolated app context with minimal data exposure.

🌐 Internet-Facing: HIGH - Remote exploitation possible without authentication, affecting internet-connected OpenHarmony devices.
🏢 Internal Only: MEDIUM - Internal network exploitation still possible but requires attacker foothold in network.

🎯 Exploit Status

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

Use-after-free vulnerabilities typically require specific memory manipulation knowledge but remote exploitation lowers barrier. No public exploit code confirmed.

🛠️ 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 applied successfully.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate OpenHarmony devices from untrusted networks and internet access

Application Restrictions

all

Disable or restrict pre-installed app network permissions where possible

🧯 If You Can't Patch

  • Implement strict network access controls to limit device exposure
  • Monitor for unusual process behavior or network connections from pre-installed apps

🔍 How to Verify

Check if Vulnerable:

Check OpenHarmony version: if v4.0.0 or earlier, device is vulnerable

Check Version:

Check device settings or use 'getprop ro.build.version.ohos' if available

Verify Fix Applied:

Confirm version is v4.0.1 or later and no unusual app behavior observed

📡 Detection & Monitoring

Log Indicators:

  • Unusual process spawns from pre-installed apps
  • Memory access violations in system logs
  • Unexpected network connections from system apps

Network Indicators:

  • Suspicious outbound connections from OpenHarmony devices
  • Unusual traffic patterns to/from pre-installed app ports

SIEM Query:

source="openharmony" AND (event_type="process_creation" AND parent_process="system_app") OR (event_type="network_connection" AND dest_ip!=expected_range)

🔗 References

📤 Share & Export