T09 · Insecure Skill Coding Practices
- Location
SKILL.md:61- Finding
Full Browser Session Cookie Is Collected Through Chat and Stored in Plaintext
- Content
View full analysis
", "created_at": "<当前ISO时间>", "auto_reply": true, "simulate_typing": false, "heartbeat_interval": 15, "message_expire_time": 300000 } ``` ``` `references/cookie_guide.md:23-30` reinforces disclosure of the entire credential: ```markdown 4. **找到 Cookie** - 在请求列表中随便点一个请求(优先选 `.json` 或 `XHR` 类型) - 在右侧找到「请求标头 / Request Headers」部分 - 找到 `Cookie:` 这一行 - 它的值是一长串文本,格式类似:`key1=value1; key2=value2; key3=value3` 5. **复制 Cookie** - 双击 Cookie 值全选,然后 `Ctrl+C`(或 `Cmd+C`)复制 - 粘贴发给 AI 助手即可 ``` ### Technical Analysis The requested cookie is an authenticated browser-session credential, not merely a low-privilege identifier. The implementation subsequently uses values such as `cookie2`, `_m_h5_tk`, `XSRF-TOKEN`, and `unb` to authenticate API and WebSocket operations. Requesting the entire cookie through an AI chat creates an additional exposure boundary. Depending on the agent platform, the credential may be retained in conversation history, execution traces, support logs, model-provider records, or audit telemetry. This conflicts with the documentation's broad assertion that the cookie is not uploaded. T ...[truncated 1824 chars]- Remediation
View remediation
