Cli Bridge
Monthly
Path traversal through dangling symlinks in anshupriyan CLI Bridge prior to 0.0.2 lets attackers who can drive the write_file MCP tool write arbitrary files outside the configured WORKSPACE_ROOT, an integrity-only impact bounded by the privileges of the user running the server. The flaw sits in resolveSafePath: when fs.realpathSync throws ENOENT because a symlink's target does not yet exist, the fallback validates only the parent directory and returns the symlink path as safe, so the subsequent write follows the link out of the sandbox. The project released a fix in 0.0.2 via PR #3 and commit 284a84c, and the independent assessment rates this local-vector (AV:L), unauthenticated, no-interaction integrity impact; no public exploit code or KEV-listed active exploitation was identified at time of analysis.
Path traversal through dangling symlinks in anshupriyan CLI Bridge prior to 0.0.2 lets attackers who can drive the write_file MCP tool write arbitrary files outside the configured WORKSPACE_ROOT, an integrity-only impact bounded by the privileges of the user running the server. The flaw sits in resolveSafePath: when fs.realpathSync throws ENOENT because a symlink's target does not yet exist, the fallback validates only the parent directory and returns the symlink path as safe, so the subsequent write follows the link out of the sandbox. The project released a fix in 0.0.2 via PR #3 and commit 284a84c, and the independent assessment rates this local-vector (AV:L), unauthenticated, no-interaction integrity impact; no public exploit code or KEV-listed active exploitation was identified at time of analysis.