T09 · Insecure Skill Coding Practices
- Location
SKILL.md:63- Finding
Plaintext Storage of an Authentication Session Cookie
- Content
View full analysis
" ``` The source instructs users to place their complete Juejin authentication cookie directly in `~/.openclaw/workspace/JUEJIN.md`. ### Technical Analysis An authenticated session cookie is a bearer credential: possession may be sufficient to submit requests with the privileges of the corresponding logged-in session. The documented configuration stores this credential as plaintext in a workspace file. The Skill does not prescribe restrictive file permissions, encryption, an operating-system credential store, access isolation, output redaction, or secure deletion. Because the file is placed under a shared Agent workspace, other local Skills, processes, backup tools, or users with workspace read access may be able to retrieve it. ### Attack Path 1. The user copies the complete cookie from an authenticated browser session. 2. The user stores it in `~/.openclaw/workspace/JUEJIN.md` as instructed. 3. Another local process, Skill, or user with read access opens the plaintext configuration file. 4. The cookie is extracted and replayed in requests to Juejin. 5. The attacker performs actions permitted by the session, potentially including creating or publishing content as the victim. Exploitation requires access to the configuration file or another disclosure mechanism. The precise account privileges available depend on the permissions and validity of the captured Juejin session. ### Impact Assessment Disclosure may allow impersonation of the affected Juejin session. Potential impact includes unauthorized draft creation, publication of attacker-controlled articles, modification of content where allowed by the session, reputational harm, and abuse of the victim's account identity. The exposure is limited to the priv ...[truncated 94 chars]- Remediation
View remediation
