T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:30- Finding
Broad Access to Durable Memory and Cross-Project State
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30–60
Vulnerability Type:T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumVulnerable snippet:
markdown ### 1. Load durable memory (in order) 1. **Memory index** — read the long-term memory file first (`MEMORY.md` at the workspace root). 2. **Daily notes** — read today's and yesterday's raw logs (`memory/YYYY-MM-DD.md`). 3. **Active task tracking** — check the IKKF/active-tasks dir (`*/status.md`). **Time-boxed ordering:** if you're short on time, load in this order and stop at N files (default 3) rather than reading everything — the index + today's notes + the top project doc cover most resumes. ### 2. Load project source-of-truth - For each known/active project, read its `PROJECT.md` (or the closest equivalent). - If a project lacks a PROJECT.md, note it as a gap (create one via project-doc skill). ### 3. Cross-check & resolve - Merge notes + PROJECT.md + active-task status into one mental model. - Identify: what was in progress, what's blocked, what's due. - **Stale detection** — if a project's PROJECT.md is older than the most recent daily note that mentions it, flag the drift so you don't trust outdated source-of-truth. ### 4. Produce the brief Emit a compact brief (not a dump): - **Where we are** — current state of active projects/tasks. - **In progress** — what's mid-flight, with file refs. - **Next actions** — the concrete next step for each. - **Open items / blockers** — anything waiting on the owner or an external dependency. - **Due soon** — upcoming deadlines or scheduled jobs. ### 5. Resume - Act on the highest-priority next action, or report the brief and wait for direction. - **Verify before trusting** — every claim in the brief should trace to a file you actually read this session. If you can't point to the source, flag it as unverified (ties into anti-hallucination). ...[truncated 1943 chars]- Remediation
View remediation
Remediation Suggestions
- Require explicit user approval before reading long-term memory or daily logs.
- Restrict reads to the current project and files explicitly named by the user.
- Replace the wildcard task lookup with an allowlisted project path.
- Do not enumerate every known project by default; require explicit project selection.
- Add redaction rules for credentials, personal information, private notes, and unrelated project data.
- Offer a metadata-only mode that reports file availability and modification times without reading contents.
- Mark each brief item with its source and suppress information outside the authorized project scope.
- Keep raw memory content out of generated responses and return only the minimum status information necessary.
