T05 · Unauthorized Access and Privilege Escalation
- Location
agents/openai.yaml:7- Finding
Implicit Invocation Permits Broad Inspection of Sensitive Local Agent Data
- Content
View full analysis
Vulnerability Details
File Locations:
agents/openai.yaml:7;SKILL.md:20-21;SKILL.md:31-37
Vulnerability Type:T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumRelevant code from
agents/openai.yaml:7:yaml policy: allow_implicit_invocation: trueRelevant code from
SKILL.md:20-25:markdown - Read local memory, daily notes, learnings, skill files, and relevant workspace context. - Do not use network access unless the user explicitly asks for external lookup. - Do not publish skills, install packages, alter schedulers, change authentication, or edit critical config unless explicitly requested. - Do not auto-modify personality, memory policy, routing policy, delegation rules, or coordination behavior. Propose changes first. - Prefer reversible edits and written rationale. - Treat private user data as sensitive. Summarize patterns; do not quote secrets or full private logs.Relevant code from
SKILL.md:31-37:markdown - Durable memory files: operating preferences, identity, durable user instructions. - Daily notes: recent raw events, decisions, and repeated themes. - Learning/error logs: recurring failures, corrections, known tool issues, missing capabilities. - Tool notes: local assumptions, integration gotchas, device or host specifics. - Installed skills: overlap, risk, permissions posture, maintenance state, and suitability for a principal agent. - Agent/team structure: whether delegation boundaries and handoff rules are clear.Technical Analysis
The skill's legitimate audit function requires access to local operational data, but its configured permission model allows implicit invocation. The permitted review targets include identity data, durable user instructions, daily activity, error history, host-specific assumptions, installed capabilities, and agent topology.
The instructions include privacy safeguards and d ...[truncated 2047 chars]
- Remediation
View remediation
Remediation Suggestions
- Disable implicit activation:
yaml policy: allow_implicit_invocation: false - Require an explicit user request before beginning an audit of memory, notes, logs, or workspace data.
- Ask the user to approve a concrete source list and review objective before reading sensitive files.
- Use a default-deny path policy and permit only individually approved files or directories.
- Explicitly exclude credentials, authentication material, private conversation archives, and unrelated workspace content.
- Redact secrets, identifiers, and unnecessary personal details before placing source material in model context or output.
- Record which sources were inspected so the audit remains reviewable and attributable.
- Preserve the existing restrictions against network access, publishing, package installation, scheduler changes, and authentication changes.
- Disable implicit activation:
