T05 · Unauthorized Access and Privilege Escalation
Error
- Location
SKILL.md:76- Finding
Overbroad Gmail Searches and Full-Thread Access Violate Least Privilege
- Content
View full analysis
" --max 10 --account ``` Brands often respond from a different person at the same company. Check for ANY email from that domain since the pitch date. **Check 3: Search sent folder for user follow-ups** ```bash gog gmail search "to: OR to:@" --max 10 --account ``` Check if the user already sent a response, follow-up, or forwarded the thread. **Check 6: Read full email threads** For any matching threads, read the FULL thread content — not just the latest message. Context changes mid-thread. ```bash gog gmail get --account ``` ``` ### Technical Analysis The Skill instructs the Agent to search incoming and outgoing email using an entire contact domain and then read the complete contents of matching threads. This access is broader than necessary to determine whether a specific tracked pitch received a reply. A company domain can appear in messages involving unrelated employees, contracts, legal discussions, invoices, credentials, personal information, or other confidential business activity. Domain-level matching therefore does not reliably constrain the search to the pitch being reviewed. Reading every matched thread further increases exposure by loading complete conversations into the Agent context rather than only the relevant reply metadata or pitch thread. The use of `--max 10` limits the number of returned search results but does not establish an authorization boundary or guarantee that those results concern the tracked pitch. ### Attack Path 1. A pitch tracker contains a contact whose email uses a shared corporate domain. 2. The Skill derives the domain and performs `from:@- Remediation
View remediation