T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:17- Finding
Insufficient Authorization Controls for Sensitive Memory and Archived Chat Access
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17–22 and 49–56
Vulnerability Type: Sensitive local-data access without enforceable identity or authorization validation
Risk Level: MediumRelevant Source Snippet (English translation):
markdown | Trigger scenario | Data to read | Purpose | |------------------|--------------|---------| | Rebuild after memory loss | Daily reports from the last seven days | Rebuild work context | | Start of each day | Today's daily report | Determine what work should continue | | Locate historical information | Index for the specified date | Locate the target file | | The named user asks about progress | Corresponding personal directory | Check the named user's progress | | Retrieve shared knowledge | Hot/warm storage | Obtain reference content | | Retrieve chat history | Cold storage | Triggered only by an instruction from the named user, manually, no more than 50 KB | ## Cold-Storage Read Rules - Write without automatic retrieval: Do not proactively read raw chats from cold storage. - Trigger: The named user says “retrieve...” - Safety limit: No more than 50 KB per operation; read in segments. - After vector search becomes available: Enable full-text retrieval as a future capability.Technical Analysis
The Skill permits access to daily reports, personal progress directories, indexed historical files, and raw archived conversations. Its authorization model relies on conversational recognition of a particular user name or trigger phrase rather than an authenticated identity, explicit owner consent, or an enforceable access-control decision.
The documented 50 KB read limit is a data-volume restriction rather than an authorization control. It does not prevent an unauthorized requester from initiating the read, and the documentation does not impose a cumulative limit that would prevent repeated segmented requests. The index-based lookup process also ...[truncated 1687 chars]
- Remediation
View remediation
Remediation Suggestions
- Require authenticated caller identity and an explicit authorization decision before reading personal directories, historical memory, or archived chats. Do not treat a claimed name or trigger phrase as proof of identity.
- Require explicit, scope-specific owner consent for raw conversation retrieval, including the requested date range, data category, and intended recipient.
- Define an allowlist of permitted directories and canonicalize each resolved path before access. Reject absolute paths, traversal components, symlink escapes, and index entries that resolve outside approved roots.
- Apply least-privilege access controls so the Skill can read only the minimum records needed for the current authorized task.
- Add content filtering and redaction for credentials, secrets, personal data, and information belonging to unrelated third parties before returning retrieved content.
- Replace the per-request-only limit with cumulative limits per user, session, and time window. Require renewed authorization when the approved scope is exceeded.
- Record tamper-resistant audit events containing the verified requester, authorization result, data category, approved scope, files accessed, and amount returned.
- Fail closed when identity, consent, ownership, or path scope cannot be verified.
