CVE-2025-55524

7.3 HIGH

📋 TL;DR

Agent-Zero v0.8.* has insecure permissions that allow attackers to trigger arbitrary system resets. This vulnerability affects all systems running vulnerable versions of Agent-Zero, potentially causing service disruption and data loss.

💻 Affected Systems

Products:
  • Agent-Zero
Versions: v0.8.*
Operating Systems: All platforms running Agent-Zero
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of affected versions are vulnerable due to insecure permission configuration in the restart functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system downtime, data corruption, and potential privilege escalation if restart process has elevated permissions.

🟠

Likely Case

Service disruption, temporary unavailability of Agent-Zero functionality, and potential data loss from interrupted operations.

🟢

If Mitigated

Minimal impact if proper access controls and monitoring are implemented to prevent unauthorized restart attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Based on CWE-732 (Incorrect Permission Assignment for Critical Resource) and description mentioning unspecified vectors, exploitation likely requires minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: Yes

Instructions:

1. Monitor official Agent-Zero repository for security updates
2. Apply patch when available
3. Restart Agent-Zero service after patching

🔧 Temporary Workarounds

Restrict Access to Restart Endpoint

linux

Implement network-level or application-level access controls to restrict who can access the restart functionality.

# Example: Use firewall rules to restrict access
# iptables -A INPUT -p tcp --dport [AGENT_PORT] -s [TRUSTED_IPS] -j ACCEPT
# iptables -A INPUT -p tcp --dport [AGENT_PORT] -j DROP

Implement Authentication Requirements

all

Add authentication checks to the restart endpoint if not already present.

# Modify restart.py to require authentication
# Example: Add @require_auth decorator or similar

🧯 If You Can't Patch

  • Isolate Agent-Zero instances in separate network segments with strict access controls
  • Implement comprehensive monitoring and alerting for unauthorized restart attempts

🔍 How to Verify

Check if Vulnerable:

Check Agent-Zero version and verify if running v0.8.* series. Review restart.py permissions and access controls.

Check Version:

agent-zero --version or check package metadata

Verify Fix Applied:

Test restart functionality with unauthorized credentials/access to ensure proper authentication and authorization checks are in place.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to restart endpoint
  • Unexpected system restart events
  • Failed authentication attempts on restart functionality

Network Indicators:

  • Unusual traffic patterns to restart API endpoint
  • Requests to restart endpoint from unauthorized sources

SIEM Query:

source="agent-zero" AND (event="restart" OR endpoint="/restart") AND result="success" AND user NOT IN [authorized_users]

🔗 References

📤 Share & Export