T05 · Unauthorized Access and Privilege Escalation
- Location
references/lessons-learned.md:293- Finding
Live Lexiang access-token harvesting from WorkBuddy application logs
- Content
View full analysis
/workbuddyMainThread__*.log by finding the latest line containing X-Oneid-Access-Token. Self-check: Always obtain the latest token from the logs. ``` ### Technical Analysis These instructions tell the Agent to search another application's logs for a live bearer token and use it for direct HTTP requests. This bypasses supported credential delegation and authentication interfaces. The behavior violates least privilege because archival does not require exposing the raw token to the Agent, its shell commands, or its conversational context. The same project provides a safer approach through delegated Lexiang tools and the authenticated uploader. Although the beginning of `lessons-learned.md` describes direct MCP access as historical, this section still calls log extraction the correct method and repeats it as a mandatory self-check. That contradiction may cause an Agent to follow the unsafe instruction. ### Attack Path 1. An attacker or user requests an archival operation in a WorkBuddy sandbox. 2. The Skill requires the Agent to read `references/lessons-learned.md`. 3. The Agent follows the instruction to search `~/.workbuddy/logs/`. 4. It extracts the latest `X-Oneid-Access-Token` value. 5. The raw bearer token enters Agent context, shell history, or HTTP request construction. 6. A malicious prompt, compromised tool, or observer can reuse the token to access Lexiang resources within the token's authorization scope. ### Impact Assessment Successful exploitation can expose an active Lexiang bearer token and permit A ...[truncated 242 chars]- Remediation
View remediation
