| Title | Goclaw V0.4.0 Command execution |
|---|
| Description | GoClaw does not reject the unauthenticated connection if the token is wrong, but reduces the connection to an authenticated viewer. The permission engine mistakenly defaults many unexplicitly classified RPC methods as viewer accessible, resulting in low-privilege sessions still being able to read channels.instances.list, directly get the original agent_id (UUID) and call logs.tail to subscribe to the server-side logs, calling heartbeat.set / heartbeat.checklist.set / heartbeat.test, the heartbeat runner injects the prompt and HEARTBEAT.md written by the attacker into the agent execution stream. If the target agent has the exec tool capability, it will eventually fall to the host machine sh -c to form command execution. |
|---|
| Source | ⚠️ https://github.com/nextlevelbuilder/goclaw/issues/866 |
|---|
| User | AiSec (UID 97073) |
|---|
| Submission | 04/13/2026 09:24 (3 months ago) |
|---|
| Moderation | 04/30/2026 16:51 (17 days later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 360314 [nextlevelbuilder GoClaw/GoClaw Lite up to 3.8.5 RPC improper authorization] |
|---|
| Points | 20 |
|---|