T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:70- Finding
Unbounded Automatic Persistence of Conversation-Derived Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:70-87; related instructions indocs/setup.md:13-23anddocs/setup.md:29-41
Vulnerability Type: Standing filesystem read/write authority without explicit consent or scope controls
Risk Level: MediumVulnerable Code Snippets
SKILL.md:70-87:markdown The AI does not wait for commands. The AI reads the system, understands the human, and acts proactively. Reviews keep the system alive. Without regular reviews, the system becomes stale. Decisions are the most valuable content. Log them with context. ## Files Every personal-os has these core files: - `STATE.md` — current project states - `TODO.md` — active tasks - `DECISIONS.md` — decision log - `PENDING-DECISIONS.md` — blocked decisions - `HEARTBEAT-LOG.md` — system activity log ## For AI Collaborators Read the personal-os after each conversation. Update relevant files. The system stays current because the AI keeps it current.docs/setup.md:13-23:markdown 3. **Start working with your AI collaborator** 4. **Update the system after each significant conversation or action** ## For the AI After each conversation: 1. Read `STATE.md`, `DECISIONS.md`, `TODO.md` 2. Update relevant files with new decisions, progress, or changes 3. Write a summary to `HEARTBEAT-LOG.md` 4. Generate review drafts periodicallydocs/setup.md:29-41:markdown ## Cron Jobs (Optional) Set up periodic health checks and review generation: - Every 30 min: consistency check - Every 1 hour: system maintenance - Every day: review generation - Every week: deeper review ## No Command Required The AI should not wait for commands. The AI reads the system, understands the human, and acts proactively.Technical Analysis
The Skill gives the agent standing authority to read persistent project records and write conversation-derived information after every ...[truncated 3039 chars]
- Remediation
View remediation
Remediation Suggestions
-
Require explicit consent for persistence
- Ask for confirmation before writing conversation-derived information.
- Present the target file and exact proposed diff before applying changes.
- Permit automatic writes only after the user explicitly enables them for a defined scope.
-
Enforce filesystem boundaries
- Configure one canonical workspace root.
- Resolve and validate paths before every operation.
- Reject absolute paths, parent-directory traversal, and symbolic-link escapes.
- Use an allowlist for files and directories the Skill may read or modify.
-
Apply data-minimization rules
- Do not persist passwords, API keys, authentication tokens, financial information, health data, or other sensitive personal information.
- Redact likely secrets before proposing a write.
- Store only the minimum context necessary for the requested task.
-
Separate trusted instructions from captured content
- Treat imported notes, webpages, emails, and document contents as untrusted data.
- Never convert instructions found inside captured content into agent policies or autonomous actions.
- Require user confirmation before promoting untrusted material into durable decision or task records.
-
Add integrity and recovery controls
- Use atomic writes and maintain version history.
- Record the source, timestamp, and approving user for each update.
- Provide simple rollback and deletion procedures.
- Avoid overwriting existing entries when an append-only record is sufficient.
-
Constrain unattended maintenance
- Disable periodic maintenance by default.
- Require explicit configuration for every scheduled operation.
- Run maintenance with least-privilege access limited to the approved workspace.
- Generate review drafts without automatically changing authoritative project state.
-
**Clarify the Skill instruct ...[truncated 284 chars]
-
