T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:6- Finding
Overly Broad Tool-Profile Escalation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 6–11
Vulnerability Type: Unauthorized access and privilege escalation
Risk Level: HighVulnerable Code Snippet:
text Diagnosing exec deny: 1. Check tools.exec.security and tools.profile in config 2. If profile=coding and security=full still denied → profile baseline missing exec 3. Use gateway tool: gateway('config.patch', {raw: '{tools:{profile:"full"}}'}) 4. Hot-reload applies automatically in hybrid mode; explicit restart via gateway restart if needed 5. Verify: gateway('config.get', {}) → confirm profile=fullTechnical Analysis
The Skill responds to an execution denial by directing the Agent to change the complete tools profile to
full. This bypasses least-privilege controls rather than narrowly correcting the missing executable allowlist entry. The subsequent hot reload makes the broader permissions effective immediately.An execution denial is a security-boundary decision. Treating it as a reason to enable a globally permissive profile may expose unrelated tools and execution capabilities that are not legitimately required for the original task. Although the document does not contain an executable payload, an Agent following these instructions could weaken its own access controls and increase the effect of later malicious or untrusted instructions.
Attack Path
- A requested command is denied by the existing execution policy.
- The Skill interprets the denial as a missing capability in the
codingprofile. - The Agent invokes
gateway('config.patch', ...)and setstools.profiletofull. - Hybrid-mode hot reload applies the configuration change without requiring a deliberate restart.
- The Agent verifies that the unrestricted profile is active.
- A subsequent untrusted prompt, compromised Skill, or unsafe operation can use the newly exposed tools and command-execution capabilities.
Impact Assessment
...[truncated 723 chars]
- Remediation
View remediation
Remediation Suggestions
- Preserve the restrictive
codingprofile and add only the exact required executable, subcommand, and argument patterns to a scoped allowlist. - Do not recommend
tools.profile: fullas the default response to an execution denial. - Require explicit, informed user or administrator approval before broadening any security profile.
- Before applying a configuration change, display the effective permission delta and explain which additional tools will become available.
- Use the documented hash-verified patch workflow to prevent stale or conflicting changes.
- Add a time-limited elevation mechanism that automatically restores the original profile after the approved operation.
- Verify the narrowly scoped permission after modification and document a rollback procedure.
- Audit and log profile changes, including the requester, justification, prior value, new value, and restoration status.
- Preserve the restrictive
