T09 · Insecure Skill Coding Practices
- Location
SKILL.md:62- Finding
Persistent Storage of Sensitive Health Data Without Adequate Privacy Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:62-82;api/profile_inquired.md:27-31
Vulnerability Type: Unprotected persistent storage of sensitive health information
Risk Level: MediumVulnerable Instructions
The following is a faithful English rendering of the complete relevant segment from
SKILL.md:62-82:markdown First check whether the local `hc_profile.md` file exists: - If it exists: Read the existing profile data and confirm whether the information needs to be updated. - If it does not exist: Collect the user's basic health data according to the rules in `api/profile_inquired.md`. After collection, save it to `hc_profile.md` in JSON format. Information to collect (10 items): | Name | Key | |---|---| | Genetic and family history | geneticHistory | | Age | age | | Sex | gender | | High-salt diet | isHighSalt | | Overweight or obesity | isFat | | Sedentary lifestyle or insufficient exercise | isLackExercise | | Staying up late or severe sleep deprivation | isLackSleep | | High stress, anxiety, or irritability | hasStress | | Smoking or excessive alcohol consumption | isSmokerDrink | | High-fat and high-sugar diet | isHighOilSugar | Note: All collected data must be stored in long-term memory using the `update_memory` tool so that it can be retrieved in subsequent conversations.The storage instruction in
api/profile_inquired.md:27-31additionally states:markdown Ensure that the JSON is displayed in pretty format. Store the JSON data generated above by overwriting: `./hc_profile.md`Technical Analysis
The Skill collects health and behavioral information including age, sex, family medical history, obesity, sleep patterns, stress, smoking, alcohol use, diet, and blood-pressure context. This is sensitive personal health information.
The instructions require the data to be persisted through two separate mechanisms:
- A predictable ...[truncated 2473 chars]
- Remediation
View remediation
Remediation Suggestions
- Default to session-only processing and do not persist health information unless persistence is necessary for a user-requested feature.
- Obtain explicit, informed, opt-in consent before storage. Request separate consent for local storage and long-term Agent memory.
- Remove the unconditional
update_memoryrequirement and avoid storing duplicate copies. - Collect only the minimum fields needed for the immediate assessment.
- Replace the predictable shared Markdown path with a user-scoped, access-controlled data store.
- Encrypt sensitive records at rest and restrict access to the current authenticated user.
- Define and enforce a short retention period.
- Provide commands for users to inspect, correct, export, and permanently delete their records.
- Bind every profile to a verified user or session identity and reject retrieval when identity isolation cannot be guaranteed.
- Validate the schema and prevent stale or cross-user data from being treated as the current user's medical profile.
- Clearly disclose what information is collected, why it is needed, where it is stored, and who can access it.
