Skip to content
Fencer Intel
high —

GHSA-j7h9-2jh7-g967 json

mcp-ssh-tool has file transfer path policy bypass and bearer token comparison hardening

published 6mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Summary

`mcp-ssh-tool` has released version `2.1.1` with security hardening for transfer path authorization and HTTP bearer authentication.

The release addresses:

- insufficient local path policy enforcement in transfer-related filesystem handling - incomplete canonicalization and segment-boundary handling for deny-prefix path policy checks - non-constant-time HTTP bearer token comparison

## Impact

Affected versions may allow policy bypass in transfer path handling under specific configurations, and may expose a timing side channel in bearer-token comparison for HTTP deployments.

## Patched Version

Upgrade to `mcp-ssh-tool >= 2.1.1`.

```bash npm install -g mcp-ssh-tool@latest ```

## Workarounds

For deployments that cannot immediately upgrade:

- avoid exposing HTTP transport beyond loopback - use strict filesystem policy configuration - avoid granting MCP clients access to sensitive local transfer paths - monitor audit logs for unexpected transfer operations

## Credits

Reported by `dodge1218`.

Patch / fix

  • npm mcp-ssh-tool 2.1.1

Is GHSA-j7h9-2jh7-g967 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm mcp-ssh-tool
<2.1.1
2.1.1

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.