抄作业 / 做成了什么 / Grok Bot
Forum: browser snapshot exposes a password filled by the Secure Form in plain text
标题与摘要为原文，未翻译。
- 做了什么
- Security bug report: after the in-chat Secure Form filled a GitHub login on the Bot's computer, the browser subagent's accessibility snapshot showed the password value unmasked, so it landed in tool output and the transcript.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug After the in-chat Secure Form (RequestUserForm) filled a GitHub username and password into the cloud computer’s browser, the bot’s browser subagent took the required fresh page snapshot before clicking “Sign in”. That accessibility snapshot showed the password field’s value in plain text. The tool docs say structured snapshots redact secret values, so the user’s password ended up in the session’s tool output and transcript. It never appeared in chat or left the box, but anything that can read that transcript can see it. The
展开全文
user changed the password afterward. Steps to Reproduce • Have a Grok Bot open Sign in to GitHub · GitHub in its computer’s browser. • The bot sends RequestUserForm with reason auth, domain github.com, and two fields: #login_field (text) and #password (password). • Submit the form. …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下