T09 · Insecure Skill Coding Practices
- Location
SKILL.md:40- Finding
Plaintext Persistent Storage of Sensitive Wedding Planning Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 40–55, with sensitive-data examples and automatic reload behavior at lines 98–112, 127–138, and 282–287
Vulnerability Type: Plaintext storage of sensitive personal information without specified access controls
Risk Level: MediumVulnerable Code Snippets
markdown All data stored locally. No cloud. No transmission. \`\`\` ~/.wedding-skill/ └── [wedding-name]/ ├── BUDGET.md # Budget tracker with actuals vs planned ├── vendors.md # All vendor details and deadlines ├── guests.md # Guest list with RSVPs and seating ├── timeline.md # Master timeline └── decisions-log.jsonl # Every decision tracked \`\`\` - **Storage location**: `~/.wedding-skill/` - **Format**: Markdown + JSONL (human-readable) - **Cloud sync**: None - **Deletion**: Remove the folder to delete all dataThe documented records can contain personal contact and contract information:
markdown Vendor: Blue Sky Photography Contact: Sarah Chen — sarah@bluesky.com Booked: March 15 Contract signed: March 20 Deposit paid: $1,500 (March 22) Balance due: $2,000 (2 weeks before wedding) Key terms: - 8 hours coverage - Second shooter included - 500+ edited photos, delivered in 6 weeks - Raw files NOT included (would be +$500) - Cancellation: 50% refund if 60+ days outThey can also contain health-related and interpersonal information:
markdown Dietary needs: - 8 vegetarian - 3 vegan - 2 gluten-free - 1 nut allergy (Sarah's cousin — FLAG for caterer) Seating constraints you've told me: ❌ Uncle Mike CANNOT sit near Aunt Linda (the divorce) ❌ Your college friends need to be near the bar ❌ Boss should be at a visible table but not family table ✅ Grandma needs to be close to the exit (mobility) ✅ Kids table near the parents but with space for chaosThe memory rules require persistent reuse:
markdown ## Memory Rules 1. **Never overwrite** — e ...[truncated 2997 chars]- Remediation
View remediation
Remediation Suggestions
- Create
~/.wedding-skill/with owner-only directory permissions (0700) and all data files with owner-only permissions (0600), explicitly overriding permissive process defaults. - Provide authenticated encryption at rest for guest, vendor, financial, health-related, and family-conflict records. Store encryption keys separately using the operating system's secure credential facility.
- Obtain explicit consent before retaining third-party contact, allergy, dietary, mobility, or interpersonal information.
- Minimize collection by storing only fields necessary for active planning. Avoid preserving free-form sensitive conversation details by default.
- Replace indefinite “never overwrite” retention with configurable retention periods, archival controls, and secure deletion.
- Support selective deletion and redaction by guest, vendor, category, or decision instead of requiring deletion of the entire directory.
- Do not automatically load every record in every session. Load only the minimum data relevant to the current request.
- Warn users that local backup, indexing, synchronization, and file-sharing software may copy plaintext records.
- Add permission validation at startup and refuse to process sensitive records if the storage directory or files are accessible to unintended users.
- Document a migration procedure that secures existing plaintext records and removes obsolete unsecured copies.
- Create
