T09 · Insecure Skill Coding Practices
- Location
scripts/init.sh:32- Finding
Predictable Shared Default Password for Agent Accounts
- Content
View full analysis
Vulnerability Details
File Location:
scripts/init.sh, lines 32–42
Vulnerability Type: Predictable hardcoded default credential
Risk Level: HighVulnerable Code
bash get_default_password() { if [ -n "$AICREDITSHARE_DEFAULT_PASSWORD" ]; then echo "$AICREDITSHARE_DEFAULT_PASSWORD" elif [ -f "${HOME}/.aicreditshare/default_password" ]; then cat "${HOME}/.aicreditshare/default_password" else echo "Test123456" # Default password fi }Technical Analysis
When neither the
AICREDITSHARE_DEFAULT_PASSWORDenvironment variable nor the local default-password file exists, the initialization script silently uses the fixed passwordTest123456. Both registration and login call this function when the user does not explicitly supply a password.The documented registration example omits a password, making it likely that users following the normal setup process will create accounts with this publicly known credential. The fallback violates secure credential-generation principles because the password is identical across installations, is present in distributed source code, and has insufficient entropy.
Attack Path
- A user follows the documented registration procedure without supplying a password.
get_default_passwordreturnsTest123456.- The script creates the remote platform account using that predictable password.
- An attacker discovers or guesses the account email address through platform activity, messages, shared task details, logs, or other sources.
- The attacker attempts to log in with the publicly known default password.
- If the platform lacks effective rate limiting or additional authentication controls, the attacker gains access to the Agent account.
Impact Assessment
Successful exploitation could grant access to the affected AI Credit Share account. Based on the capabilities exposed by the S ...[truncated 459 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the hardcoded password fallback entirely.
- Require users to supply a password explicitly, preferably through a hidden interactive prompt such as
read -s. - Alternatively, generate a unique password using a cryptographically secure random source and require the user to store it securely.
- Enforce an appropriate minimum password length and reject known or weak passwords.
- Do not reuse a default password across accounts or installations.
- Encourage or require multifactor authentication when the platform supports it.
- Add server-side login rate limiting and monitoring as defense-in-depth measures.
