T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:60- Finding
Overbroad Automatic Access and Persistent Retention of Sensitive Health Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 60, 91–93, 116, 476, and 510
Vulnerability Type: T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumVulnerable Instructions
The following English translations preserve the meaning of the relevant instructions:
text Line 60: This is a version dedicated to one user. You should use "strong memory mode" by default. Lines 91–93: - All Apple Watch / HealthKit-related data - Heart rate, resting heart rate, HRV, sleep, blood oxygen, temperature trends, respiratory rate, steps, standing time, active energy, workouts, VO2 max, etc. - During every user interaction, automatically read the latest HealthKit data for the current week as a reference for the user's recent condition. Line 116: Treat the information above as a continuously updated long-term database rather than isolated pieces of information. Line 476: First retrieve and integrate all previously known health information and related personal information about the user. Line 510: By default, integrate and remember all health information and related personal information provided by the user for long-term analysis.Technical Analysis
The skill directs the agent to retrieve current HealthKit information during every interaction, aggregate all previously known health and personal information, and retain that information under a default “strong memory” model.
These instructions violate least-privilege and data-minimization principles because access is not limited to information necessary for the user's current request. The requested scope includes medical history, mental state, reproductive information, wearable measurements, lifestyle information, medication use, and related personal background.
The document does not define:
- Explicit, informed opt-in before each HealthKit or historical-record access
- Field-level or purpose-based access restr ...[truncated 2556 chars]
- Remediation
View remediation
Remediation Suggestions
-
Require explicit consent
- Ask for informed opt-in before accessing HealthKit or historical health records.
- Explain which source, date range, and metrics will be accessed.
- Do not treat prior consent as permanent authorization for unrelated requests.
-
Apply data minimization
- Retrieve only the fields necessary for the current question.
- Replace “all HealthKit-related data” with a narrowly scoped list selected according to the user's request.
- Avoid retrieving historical personal information unless it is materially relevant.
-
Disable default persistent memory
- Make long-term storage opt-in rather than the default.
- Permit one-time analysis without retaining the supplied records.
- Store concise derived summaries instead of raw medical records where feasible.
-
Add retention and deletion controls
- Define a clear expiration period for retained information.
- Allow users to inspect, correct, export, and delete stored health information.
- Ensure deletion covers raw data, summaries, indexes, and derived memory entries.
-
Enforce least privilege
- Request only the minimum tool permissions needed for each operation.
- Restrict HealthKit access by metric and time range.
- Prevent health-data retrieval during unrelated interactions.
-
Protect sensitive records
- Require encryption in transit and at rest.
- Isolate each user's records and enforce authenticated access.
- Avoid placing raw health data in logs, telemetry, or diagnostic traces.
-
Provide access transparency
- Disclose which historical records and connected sources were used in each analysis.
- Record auditable access events without copying sensitive record contents into logs.
-
