Disclosed weakness · no CVE recorded
A saved AgentScope Bash rule could approve additional commands
AgentScope · AgentScope · Bash permissions
First documented disclosure · Review checkpoint
Summary
A saved allow rule intended for one command could authorize other operations in the same tool call.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The public report and upstream fix document the defect. They identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
AgentScope matched the entire command string against a rule without checking each constituent operation.
Conditions required
An agent using the Bash tool in default permission mode has an applicable saved allow rule.
Potential impact
Additional operations could run under the agent’s operating-system permissions without prompting the user.
Affected versions and configurations
The project verified the pre-fix implementation. A complete affected release range was not published.
Fix and mitigation status
2.0.12 includes the correction.
Practical next steps
Upgrade to 2.0.12 or a later fixed version. Review saved Bash rules and use explicit confirmation for compound commands until upgraded.
Operating lesson
Apply a user’s saved permission to each operation it authorizes.
Evidence and limits
Issue 3512 and PR 3513 describe the saved-rule defect. The automatic filesystem-edit permission is a separate code path. The November 16 release lists the patch.
Sources
- AgentScope original issue
Primary source ·
- AgentScope merged correction
Primary source ·
- AgentScope 2.0.12 release notes
Primary source ·