Vulnerabilities

6 via 6 paths

Dependencies

393

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 3
  • 3
Status
  • 6
  • 0
  • 0

high severity
new

Inefficient Algorithmic Complexity

  • Vulnerable module: immutable
  • Introduced through: immutable@5.1.5

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard immutable@5.1.5
    Remediation: Upgrade to immutable@5.1.8.

Overview

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the HashCollisionNode class in Immutable.Map and Immutable.Set. An attacker can cause excessive CPU consumption by supplying a large number of keys with identical 32-bit hashes, leading to degraded insertion and lookup performance through crafted input objects.

Remediation

Upgrade immutable to version 4.3.9, 5.1.8 or higher.

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: immutable
  • Introduced through: immutable@5.1.5

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard immutable@5.1.5
    Remediation: Upgrade to immutable@5.1.8.

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound in the setListBounds function in src/List.js when handling an index or size in the range 2 ** 30 to 2 ** 31. An attacker can cause an empty list to enter an uncatchable infinite loop, trigger unbounded memory allocation until process abort, or cause silent value wrapping by supplying crafted input values.

Remediation

Upgrade immutable to version 4.3.9, 5.1.8 or higher.

References

high severity

Asymmetric Resource Consumption (Amplification)

  • Vulnerable module: ws
  • Introduced through: parse@8.5.0

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard parse@8.5.0 ws@8.19.0

Overview

ws is a simple to use websocket client, server and console for node.js.

Affected versions of this package are vulnerable to Asymmetric Resource Consumption (Amplification) when handling a large number of very small fragments and data chunks. An attacker can cause excessive memory allocation and OOM by sending a high volume of tiny WebSocket frames

Workaround

This vulnerability can be mitigated by lowering the value of the maxPayload option.

PoC

import { WebSocket, WebSocketServer } from 'ws';

const wss = new WebSocketServer({ port: 0 }, function () {
  const data = Buffer.alloc(1);
  const options = { fin: false };
  const { port } = wss.address();
  const ws = new WebSocket(`ws://localhost:${port}`);

  ws.on('open', function () {
    (function send() {
      ws.send(data, options, function (err) {
        if (err) return;
        send();
      });
    })();
  });

  ws.on('error', console.error);
  ws.on('close', function (code, reason) {
    console.log(`client close - code: ${code} reason: ${reason.toString()}`);
  });
});

wss.on('connection', function (ws) {
  ws.on('error', console.error);
  ws.on('close', function (code, reason) {
    console.log(`server close - code: ${code} reason: ${reason.toString()}`);
  });
});

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade ws to version 5.2.5, 6.2.4, 7.5.11, 8.21.0 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: ws
  • Introduced through: parse@8.5.0

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard parse@8.5.0 ws@8.19.0

Overview

ws is a simple to use websocket client, server and console for node.js.

Affected versions of this package are vulnerable to Use of Uninitialized Resource in the websocket.close() implementation in the Sender class, which exposes uninitialized memory when a TypedArray is provided as the reason argument.

Note: The project maintainers note that this "flaw is only exploitable through misuse that is unlikely in practice".

PoC

import { deepStrictEqual } from 'node:assert';
import { WebSocket, WebSocketServer } from 'ws';

const wss = new WebSocketServer(
  { port: 0, skipUTF8Validation: true },
  function () {
    const { port } = wss.address();
    const ws = new WebSocket(`ws://localhost:${port}`, {
      skipUTF8Validation: true
    });

    ws.on('close', function (code, reason) {
      deepStrictEqual(reason, Buffer.alloc(80));
    });
  }
);

wss.on('connection', function (ws) {
  ws.close(1000, new Float32Array(20));
});

Remediation

Upgrade ws to version 8.20.1 or higher.

References

medium severity
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: body-parser
  • Introduced through: body-parser@2.2.2

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard body-parser@2.2.2
    Remediation: Upgrade to body-parser@2.3.0.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to invalid limit option handling in normalizeOptions in lib/utils.js. An attacker can force oversized request bodies through by supplying an application configuration value for limit that parses to null, such as an unparseable string or NaN. When an app relies on limit to cap body size, the parser skips enforcement and accepts arbitrarily large payloads, driving excessive memory and CPU usage and degrading or crashing the service.

Remediation

Upgrade body-parser to version 1.20.6, 2.3.0 or higher.

References

medium severity
new

Cross-site Request Forgery (CSRF)

  • Vulnerable module: react-router
  • Introduced through: react-router@7.18.1

Detailed paths

  • Introduced through: parse-dashboard@parse-community/parse-dashboard react-router@7.18.1
    Remediation: Upgrade to react-router@8.3.0.

Overview

Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) via the unstable RSC APIs. An attacker can execute unauthorized actions by tricking a user into submitting crafted requests.

Note: This is only exploitable if the unstable RSC APIs are enabled in the application.

Remediation

Upgrade react-router to version 8.3.0 or higher.

References