Skip to content
Fencer Intel
high —

GHSA-r4m5-47cq-6qg8 json

Server-Side Request Forgery in ftp-srv

published 6y ago modified 2y 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

All versions of `ftp-srv` from v1.0.0 onward to v4.3.3 are vulnerable to Server-Side Request Forgery (SSRF). The package fails to prevent remote clients to access other resources in the network, for example when connecting to the server through telnet. This allows attackers to access any network resources available to the server, including private resources in the hosting environment.

## Recommendation

Upgrade to patched versions `^2.19.6, ^3.1.2, ^4.3.4`

## Workarounds Blacklisting the FTP Command PORT will prevent the server from exposing this behaviour through active connections until a fix is applied.

``` const ftp = new FtpSrv({ blacklist: ['PORT'] }); ```

Patch / fix

  • npm ftp-srv 2.19.6, 3.1.2, 4.3.4

Is GHSA-r4m5-47cq-6qg8 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 ftp-srv
>=1.0.0, <2.19.6
>=3.0.0, <3.1.2
>=4.0.0, <4.3.4
2.19.6
3.1.2
4.3.4

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

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.