T09 · Insecure Skill Coding Practices
- Location
SKILL.md:81- Finding
Plaintext Persistent Storage of Sensitive Personal Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 81-116 and 163-172
Vulnerability Type: Plaintext storage of sensitive personal and third-party information
Risk Level: HighVulnerable Documentation
The Skill prescribes persistent JSON storage using the following structure:
text /memory/life-memories/people/[person-name].json /memory/life-memories/upcoming-events.json /memory/life-memories/follow-ups.json /memory/life-memories/master-index.jsonThe documented person record includes identifying information, preferences, allergies, birthdays, conversation summaries, and action items. The privacy rules also explicitly permit storage of sensitive health, financial, relationship-conflict, and third-party information after confirmation.
Technical Analysis
The Skill directs the Agent to create persistent personal profiles in ordinary JSON files. No encryption at rest, restrictive file permissions, access-control checks, data-retention limits, secure deletion procedures, or isolation from other Skills and local processes are specified.
The master index, event database, follow-up database, and individual person records can duplicate or reference the same sensitive information. Consequently, deleting a fact from one person record may not remove it from indexes, summaries, backups, or generated reminders.
User confirmation does not mitigate the technical exposure created after storage. The risk is particularly significant because the collected information may concern people who never interacted with or consented to the Agent.
Attack Path
- A user provides a conversation containing a birthday, allergy, health condition, financial detail, relationship conflict, or other private fact.
- The Skill instructs the Agent to extract that fact and associate it with an identified person.
- The Agent writes the information to a plaintext JSON record and may add references to the master index, e ...[truncated 870 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not store health, financial, relationship-conflict, authentication, or third-party private information by default.
- Require explicit, granular consent for each sensitive record rather than relying on general confirmation.
- Encrypt sensitive records at rest using keys stored outside the memory directory.
- Restrict files and directories to the minimum required operating-system identity, such as owner-only permissions.
- Separate indexes from sensitive record contents and avoid duplicating private facts in summaries or reminder files.
- Establish configurable retention periods and automatically purge expired records.
- Implement deletion across person records, indexes, reminders, cached summaries, and backups.
- Record provenance and consent status for every stored fact.
- Provide an inventory and export mechanism so users can review all retained information.
- Add tests verifying that sensitive data is neither logged nor exposed through generated reminders.
