CVE-2024-49357

7.5 HIGH

📋 TL;DR

ZimaOS versions 1.2.4 and earlier expose sensitive system and application data through unauthenticated API endpoints. Attackers can access detailed information about installed applications and system configuration without any credentials. All ZimaOS users running vulnerable versions are affected.

💻 Affected Systems

Products:
  • ZimaOS
Versions: 1.2.4 and all prior versions
Operating Systems: ZimaOS
Default Config Vulnerable: ⚠️ Yes
Notes: Affects both Zima devices and x86-64 systems with UEFI running ZimaOS. The vulnerability exists in the default configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers gain complete reconnaissance of the system, enabling targeted attacks against known vulnerabilities in exposed applications or using leaked configuration data for privilege escalation.

🟠

Likely Case

Information disclosure allows attackers to map the system environment, identify vulnerable software versions, and plan subsequent attacks based on discovered applications and configurations.

🟢

If Mitigated

With proper network segmentation and access controls, the impact is limited to information disclosure within the isolated network segment.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires only HTTP requests to specific endpoints. A YouTube demonstration video is available showing the vulnerability.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: None available

Vendor Advisory: https://github.com/IceWhaleTech/ZimaOS/security/advisories/GHSA-hg2h-q5h6-r5c4

Restart Required: No

Instructions:

No official patch is available. Monitor the vendor advisory for updates and apply when released.

🔧 Temporary Workarounds

Network Access Control

linux

Restrict network access to ZimaOS API endpoints using firewall rules

iptables -A INPUT -p tcp --dport 80 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j DROP

Reverse Proxy Authentication

all

Place ZimaOS behind a reverse proxy that requires authentication

🧯 If You Can't Patch

  • Isolate ZimaOS systems on separate network segments with strict access controls
  • Implement network monitoring for unauthorized access attempts to the vulnerable endpoints

🔍 How to Verify

Check if Vulnerable:

Test if unauthenticated access to http://<ZimaOS-IP>/v1/users/image?path=/var/lib/casaos/1/app_order.json returns sensitive data

Check Version:

Check ZimaOS version through web interface or system information

Verify Fix Applied:

Verify that the same endpoint now requires authentication or returns an error when accessed without credentials

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests to /v1/users/image endpoint with path parameter
  • Unauthenticated access attempts to sensitive API endpoints

Network Indicators:

  • Unusual HTTP GET requests to /v1/users/image?path= from unauthorized IP addresses
  • Traffic patterns showing reconnaissance activity

SIEM Query:

source="zimaos" AND (url="/v1/users/image" OR url CONTAINS "app_order.json" OR url CONTAINS "system.json")

🔗 References

📤 Share & Export