T09 · Insecure Skill Coding Practices
- Location
SKILL.md:111- Finding
Unsafe Handling of Exported Browser Session Cookies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 111-127
Vulnerability Type: Exposure and insecure handling of authentication cookies
Risk Level: MediumVulnerable Documentation Segment
The following is an English rendering of the complete affected segment:
text ## Platforms Requiring Configuration Some platforms require login cookies (tell the Agent, "Help me configure XXX"): | Platform | Configuration method | |----------|----------------------| | Twitter | Cookie | | Xiaohongshu | Cookie | | Reddit | rdt login | | LinkedIn | Cookie | Configuration process: 1. Log in to the target website through a browser. 2. Export the cookies with the Cookie-Editor extension. 3. Tell the Agent, "Help me configure Twitter, Xiaohongshu, etc."Technical Analysis
Exported browser cookies can contain active authentication session tokens. Possession of such a token may allow a party to use the corresponding account without knowing the password or completing the normal authentication flow.
The documented workflow directs users to export cookies through a browser extension and then involve the Agent in configuring the affected service. It does not specify a secure secret-input channel, approved storage destination, restrictive file permissions, log redaction, expiration policy, cleanup process, or session-revocation procedure.
Consequently, a user may paste cookie contents into an Agent conversation or allow them to appear in tool arguments, command history, execution traces, logs, or insecure configuration files. This creates an avoidable credential-disclosure risk.
Attack Path
- A user signs in to Twitter, Xiaohongshu, LinkedIn, or another supported service.
- The user exports the authenticated browser cookies with the recommended browser extension.
- Following the Skill instructions, the user provides those cookies to the Agent or asks the Agent to store them during confi ...[truncated 1211 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not instruct users to paste cookie values into Agent conversations, prompts, or ordinary command arguments.
- Use a documented local secret store or a dedicated masked secret-input mechanism that prevents credentials from entering chat history and logs.
- Clearly identify the trusted tool and exact local destination receiving the cookies before requesting any configuration.
- Store cookie files with permissions limited to the owning user, such as mode
0600on supported systems. - Disable command echoing and redact cookie values from tool output, diagnostic reports, error messages, telemetry, and execution traces.
- Request only the minimum platform-specific cookies necessary for the feature instead of complete browser cookie exports.
- Never reuse a general browser profile or export unrelated cookies from other domains.
- Define retention and deletion behavior, including secure removal when configuration is replaced or no longer required.
- Warn users that cookies are authentication credentials and must not be shared through chat, tickets, screenshots, or public files.
- Provide instructions for revoking active sessions and rotating credentials after actual or suspected exposure.
- Prefer platform-supported OAuth or restricted API tokens with explicit scopes, short lifetimes, and revocation support wherever available.
