T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:13- Finding
Overbroad Access to Persistent Agent Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13-21
Vulnerability Type:T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumVulnerable Code
markdown ### Step 2: Read today's content-production records Read the current and previous day's content-production data from `memory/YYYY-MM-DD.md`: - Number of completed scripts, storyboards, and generated videos - Platform publishing activity - Team collaboration events ### Step 3: Read targets for comparison Read `memory/targets.md`, if it exists, to obtain weekly or monthly targets and compare them with actual completion.The snippet above is an English rendering of the corresponding source instructions.
Technical Analysis
The Skill instructs the Agent to read complete persistent-memory files for the current day, previous day, and team targets. Although the requested fields are relevant to producing a daily report, the instructions do not restrict access to structured fields, require user authorization, validate the selected memory paths, or require redaction of unrelated content.
Daily memory files may contain private conversation context, personal information, credentials, internal business details, or other records unrelated to production statistics. Reading the whole files places all such content in the Agent's active context and creates a risk that it may be incorporated into the generated report. This violates least-privilege principles because the Skill needs specific production metrics rather than unrestricted access to all content in those files.
No evidence indicates that the Skill modifies memory, obtains operating-system privileges, transmits information externally, or accesses arbitrary paths. The issue is therefore limited to overbroad access and potential disclosure within the generated report.
Attack Path
- Sensitive or unrelated information is stored in the current day's, previous day's, or t ...[truncated 1089 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit user authorization before reading persistent-memory files.
- Replace free-form memory access with a structured data source containing only report fields such as completed scripts, storyboards, generated videos, publishing activity, and collaboration events.
- Enforce an exact path allowlist and reject path traversal, substitutions, or references outside the designated reporting files.
- Parse only explicitly approved fields instead of loading complete file contents into the reporting context.
- Add mandatory redaction for credentials, tokens, personal data, private conversation content, and unrelated business information.
- Instruct the Agent never to reproduce memory content verbatim unless the user explicitly requests and authorizes it.
- If a required field cannot be retrieved safely, preserve the existing behavior of displaying an unavailable-value marker rather than broadening access.
- Limit report distribution to authorized recipients and review generated reports for sensitive content before publication.
