Skip to content

fix: tighten MCP config redaction and config-scan symlink handling - #191

Open
swarit-stepsecurity wants to merge 2 commits into
step-security:mainfrom
swarit-stepsecurity:swarit/chore/wt/vapt-cleanup
Open

fix: tighten MCP config redaction and config-scan symlink handling#191
swarit-stepsecurity wants to merge 2 commits into
step-security:mainfrom
swarit-stepsecurity:swarit/chore/wt/vapt-cleanup

Conversation

@swarit-stepsecurity

Copy link
Copy Markdown
Member

Small hardening fixes found during a recent assessment:

  • MCP config filtering now redacts secrets that can show up in the fields we keep (URL, args, command), not just the ones we already drop.
  • Package-manager config scans (.npmrc/.yarnrc/bunfig.toml) no longer follow symlinks encountered while walking project directories.

Both include regression tests.

env and headers were dropped outright, but a credential embedded in
the server URL or in an args flag passed through unredacted.
…cans

.npmrc/.yarnrc(.yml)/bunfig.toml discovered while walking project
directories could be a symlink to an unrelated file elsewhere on disk;
the scan would follow it and include the target's contents in the
audit. Project-scope symlinks are now recorded but not read through.
User/global/builtin scope files are unaffected.
@swarit-stepsecurity

Copy link
Copy Markdown
Member Author

cc: @ashishkurmi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant