T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:58- Finding
Mandatory Access to Sensitive Agent Memory Outside the Declared Skill Scope
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 58–68
Vulnerability Type: Least-privilege violation through unnecessary access to persistent personal data
Risk Level: MediumVulnerable Code
markdown - Interpretation/coaching remains outside this skill. ## Training Programming Reference All programming decisions must be grounded in **Practical Programming for Strength Training** (Rippetoe & Baker, 3rd Ed.). **Always load before giving any programming advice:** 1. `reference/practical-programming/INDEX.md` — who Joao is, relevant chapters, reading guide 2. `memory/training-continuity.md` — current lifts, recent sessions, health signals For any programming question, read the relevant sections of `reference/practical-programming/book.md` directly. The book is the authority.Technical Analysis
The Skill describes itself as a narrow, read-only front door for live Fitbit and training-data retrieval. It also explicitly states that interpretation and coaching are outside its scope. Despite that boundary, its instructions require the Agent to load
memory/training-continuity.md, which is described as containing current lifts, recent sessions, and health signals, whenever programming advice is requested.This requirement unnecessarily expands the information accessible to the active Agent context. It violates the principle of least privilege because the Skill can perform its documented retrieval function without loading persistent personal health and training memory. The broad instruction to “Always load” the file does not require explicit user consent, identify a minimum necessary subset, or limit how the loaded data may subsequently be used.
The reviewed files do not demonstrate that this information is transmitted externally, modified, or used to gain operating-system permissions. Therefore, the confirmed issue is unauthorized contextual access to sensitive local Agent memory rather than confirmed data exfiltration or ...[truncated 1344 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the Training Programming Reference section from this retrieval-only Skill and place coaching behavior in a separate, explicitly scoped Skill.
- Do not automatically load persistent personal memory. Request explicit user consent before accessing health or training-history data.
- Apply data minimization by reading only the specific fields and date ranges required for the current question rather than loading the entire memory file.
- Clearly document which local files may be accessed, why access is necessary, and whether their contents can be included in generated output.
- Enforce purpose limitation so retrieved health information cannot be reused for unrelated requests without renewed authorization.
- Where supported, replace direct file access instructions with a constrained interface that returns only approved, task-relevant fields.
