GHSA-8mpm-q7mh-8fvh: Capgo CLI: symlink-following local secret writes enable arbitrary file overwrite + world-readable credentials (0600 missing)
SummaryThe Capgo CLI writes sensitive local files (.capgo API key file and build credentials JSON) using unsafe file operations that follow symlinks and do not enforce safe permissions. This allows an attacker-controlled repository to cause arbitrary file overwrite on the developer’s machine when the developer runs the CLI inside that repo. Additionally, global build credentials are written with world-readable permissions (664), exposing signing materials on shared systems.DetailsIssue 1 - Arbitrary file overwrite via .capgo symlink (login --local)Location: src/login.tsBehavior: loginInternal(..., { local: true }) performs writeFileSync('.capgo', ...) before validating the API key with verifyUser().No checks are performed to prevent writing through a symlink.Result: if .capgo is a symlink to an arbitrary path, the CLI overwrites the symlink target with attacker-controlled content (the provided API key string), even when login fails.Issue 2 - Arbitrary file overwrite via .capgo-credentials.json symlink (build credentials save --local)Location: src/build/credentials.ts (local path is join(cwd(), '.capgo-credentials.json'))Behavior: credentials are written using writeFile() without checking whether the destination is a symlink.Result: if .capgo-credentials.json is a symlink to an arbitrary path, the CLI overwrites the symlink target with attacker-controlled JSON (including base64-encoded credential material). This occurs even if the user is not logged in / no API key exists.Issue 3 - Insecure default permissions for global credentialsLocation: src/build/credentials.ts (global path $HOME/.capgo-credentials/credentials.json)Observed permissions after save: -rw-rw-r-- (664)Impact: credentials file contains sensitive signing material (e.g., Android keystore + Play config; iOS cert/profile/API key in other flows). World/group readability is unsafe on shared hosts and CI runners. Expected minimum: file 0600, directory 0700.PoCPoC A: .capgo symlink clobber (writes even when API key invalid)_Expected: On invalid key, nothing is written; .capgo should never follow symlinks.
Observed: TARGET contains INVALID_KEY_SHOULD_FAIL._PoC B: .capgo-credentials.json symlink clobber (no login required)_Expected: Refuse to write if destination is symlink; ideally require safe location and permissions.
Observed: TARGET is created/overwritten with credentials JSON._PoC C: global credentials permissions are world-readable_Observed: credentials.json created with mode 664 (-rw-rw-r--)._ImpactArbitrary file overwrite (clobber) as the user running the CLI (developer workstation / CI runner).This can cause:developer environment compromise or sabotage (overwriting config files, scripts, env files)
accidental or malicious leakage/destruction of secretsLocal secret exposure: global credentials written as 664 allows other local users to read signing material on shared machines.A realistic scenario: a developer runs npx @capgo/cli ... --local inside an untrusted repo/template; the repo contains malicious symlinks.Suggested remediationDo not write .capgo until after API key validation succeeds.For all secret/config writes:refuse symlink destinations (lstat + isSymbolicLink)
use safe file creation and enforce permissions (0600 for files; 0700 for directories)
write atomically (temp file + rename) after safety checksAvoid blindly appending to .gitignore unless it is a regular file (also check for symlink).
CVSS v4.0: 8.6