T09 · Insecure Skill Coding Practices
- Location
scripts/api.js:36- Finding
Long-Lived Authentication Credentials Stored in Plaintext Files
- Content
View full analysis
({ token: localStorage.getItem('token'), tokenExpireAt: localStorage.getItem('token_expire_at'), refreshToken: localStorage.getItem('refresh_token'), refreshTokenExpireAt: localStorage.getItem('refresh_token_expire_at'), })); token = authInfo.token; await context.storageState({ path: CONFIG.authStateFile }); saveTokenCache({ token: authInfo.token, tokenExpireAt: authInfo.tokenExpireAt ? parseInt(authInfo.tokenExpireAt) : null, refreshToken: authInfo.refreshToken || null, refreshTokenExpireAt: authInfo.refreshTokenExpireAt ? parseInt(authInfo.refreshTokenExpireAt) : null, }); ``` The separate refresh utility similarly persists authentication data without explicitly restricting file permissions: ```js const authInfo = await page.evaluate(() => ({ token: localStorage.getItem('token'), tokenExpireAt: localStorage.getItem('token_expire_at'), refreshToken: localStorage.getItem('refresh_token'), refreshTokenExpireAt: localStorage.getItem('refresh_token_expire_at') })); if (!authInfo.token) { console.error('❌ Failed to get token from page. May need manual re-login.'); process.exit(1); } // Save new token fs.writeFileSync(T ...[truncated 3260 chars]- Remediation
View remediation
