GitHub Advisoryadvisory · npm

GHSA-rp42-5vxx-qpwr basic-ftp vulnerable to denial of service via unbounded memory consumption in Client.list()

HIGH Published 2026-04-16 Modified 2026-04-24 Official page ↗
Aliases
CVE-2026-41324
Ecosystem
npm
Packages
basic-ftp
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400, CWE-770
Reviewed
2026-04-16

Affected packages

• npm basic-ftp: < 5.3.0 → fixed in 5.3.0

Description

Summary `[email protected]` is vulnerable to denial of service through unbounded memory growth while processing directory listings from a remote FTP server. A malicious or compromised server can send an extremely large or never-ending listing response to `Client.list()`, causing the client process to consume memory until it becomes unstable or crashes. Details The issue is in the package's default directory listing flow. `Client.list()` reaches `dist/Client.js`, where the full listing response is downloaded into a `StringWriter` before parsing: File: `dist/Client.js:516-527` ```js async _requestListWithCommand(command) { const buffer = new StringWriter_1.StringWriter(); await (0, transfer_1.downloadTo)(buffer, { ftp: this.ftp, tracker: this._progressTracker, command, remotePath: "", type: "list" }); const text = buffer.getText(this.ftp.encoding); this.ftp.log(text); return this.parseList(text); } ``` The vulnerable sink is `StringWriter`, which grows an in-memory `Buffer` with no limit: File: `dist/StringWriter.js:5-20` ```js class StringWriter extends stream_1.Writable { constructor() { super(...arguments); this.buf = Buffer.alloc(0); } _write(chunk, _, callback) { if (chunk instanceof Buffer) { this.buf = Buffer.concat([this.buf, chunk]); callback(null); } else { callback(new Error("StringWriter expects chunks of type 'Buffer'.")); } } getText(encoding) { return this.buf.toString(encoding); } } ``` The critical operation is: ```js this.buf = Buffer.concat([this.buf, chunk]); ``` There is no maximum size check, no truncation, and no streaming parser. Because the remote FTP server controls the listing response, it can force the client to keep allocating memory until the process is terminated. How it happens: 1. An application connects to an attacker-controlled or compromised FTP server. 2. The application calls `client.list()`. 3. The server returns an extremely large or unbounded directory listing. 4. `basic-ftp` buffers the full response in `StringWriter`. 5. Memory grows without bound due to repeated `Buffer.concat(...)` calls. PoC The following PoC exercises the vulnerable buffering primitive directly: ```js const { StringWriter } = require("basic-ftp/dist/StringWriter.js"); function mb(n) { return Math.round(n / 1024 / 1024) + "MB"; } const writer = new StringWriter(); let wrote = 0; for (let i = 0; i MAX_LISTING_BYTES) { callback(new Error("FTP listing exceeds maximum allowed size.")); return; } this.buf = Buffer.concat([this.buf, chunk]); ```

Related

Alias · CVE (1)

  • CVE-2026-41324 basic-ftp is an FTP client for Node.js. vulnerability

Weakness · CWE (2)

  • CWE-400 Uncontrolled Resource Consumption weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

References