T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:11- Finding
Silent Workplace Monitoring and Overbroad Access to Local Activity Records
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:11-12,SKILL.md:24-27,SKILL.md:45-47,SKILL.md:65-67
Vulnerability Type: Excessive access to screen-derived activity data and local memory
Risk Level: MediumVulnerable Code Snippets
SKILL.md:11-12:markdown 1. **自动截屏追踪**：每15分钟截图 → AI 分析 → 写入日志 → 删图，全程静默 2. **18:00 自动日报**：每天下班主动推送当日工作日报，无需用户操作SKILL.md:24-27:markdown ### 渠道一：自动截屏分析日志（优先读取） bear 配置了每15分钟的自动化截屏系统（工作日 9:00-18:00），日志存储在：SKILL.md:45-47:markdown ### 渠道三：本地记忆文件 项目 `.workbuddy/memory/YYYY-MM-DD.md` 或 `~/.workbuddy/memory/`。SKILL.md:65-67:markdown 1. 读取当日截屏日志 `.workbuddy/screenshots/YYYY-MM-DD.md` 2. 统计各状态时长（专注/沟通/离开） 3. 按时段归纳主要工作事项Technical Analysis
The Skill instructs the agent to prioritize records produced by a screenshot-monitoring system that captures activity every 15 minutes and operates silently. It also permits reading memory from both the current project and the user's home directory. These data sources are broader and more privacy-sensitive than the minimum information needed to format user-supplied work updates.
The instructions do not define an explicit consent boundary, an application allowlist, field-level redaction, sensitivity filtering, access restrictions, or retention controls. Although screenshots are described as being deleted after analysis, their derived contents remain in activity logs and can still disclose sensitive information displayed on screen.
The home-directory path
~/.workbuddy/memory/further expands the effective read scope beyond the current project. If that directory contains unrelated historical context, the agent may incorporate it into a report without separate authorization.No executable screenshot implementation is included in the audited package, so this finding is limited to the access and processing behavior directed by the Skill. There is no evidence in the pack ...[truncated 1634 chars]
- Remediation
View remediation
Remediation Suggestions
- Disable silent screenshot tracking by default and require informed, explicit opt-in before enabling it.
- Display the capture interval, operating hours, applications covered, storage location, retention period, and intended report recipients during consent.
- Require separate authorization before reading
~/.workbuddy/memory/; default to files inside the current project and requested date range. - Apply an application allowlist and exclude password managers, authentication dialogs, private messaging tools, personal applications, and other sensitive windows.
- Perform secret and sensitive-data redaction before writing activity logs or generating reports.
- Let users review and approve screenshot-derived entries before they are included in reports or sent through automation.
- Minimize stored content to coarse activity categories rather than retaining detailed screen-derived descriptions.
- Define automatic retention and secure deletion policies for both screenshots and derived logs.
- Restrict automated reports to explicitly approved recipients and avoid including raw activity records.
- Record auditable consent and provide a visible mechanism to pause monitoring or revoke access.