Vulnerabilities

6 via 11 paths

Dependencies

417

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: performr-runner-result-graph@6.1.0

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner performr-runner-result-graph@6.1.0 immutable@3.8.3
    Remediation: Upgrade to performr-runner-result-graph@7.0.1.

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: performr-runner-result-graph@6.1.0

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner performr-runner-result-graph@6.1.0 immutable@3.8.3
    Remediation: Upgrade to performr-runner-result-graph@7.0.1.

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
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: ws
  • Introduced through: ws@7.5.13 and jsdom@16.7.0

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner ws@7.5.13
    Remediation: Upgrade to ws@8.21.1.
  • Introduced through: openrunner@computestdev/Openrunner jsdom@16.7.0 ws@7.5.13
    Remediation: Upgrade to jsdom@17.0.0.

Overview

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

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the receiver.js. An attacker can cause memory exhaustion by sending incomplete fragmented WebSocket messages, specifically by transmitting a text frame with FIN=0 followed by multiple continuation frames without completing the sequence, resulting in each fragment being stored as a separate Buffer object with significant overhead.

Remediation

Upgrade ws to version 8.21.1 or higher.

References

medium severity

Use of a Cryptographic Primitive with a Risky Implementation

  • Vulnerable module: elliptic
  • Introduced through: browserify@16.5.2

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner browserify@16.5.2 crypto-browserify@3.12.1 browserify-sign@4.2.6 elliptic@6.6.1
  • Introduced through: openrunner@computestdev/Openrunner browserify@16.5.2 crypto-browserify@3.12.1 create-ecdh@4.0.4 elliptic@6.6.1

Overview

elliptic is a fast elliptic-curve cryptography implementation in plain javascript.

Affected versions of this package are vulnerable to Use of a Cryptographic Primitive with a Risky Implementation due to the incorrect computation of the byte-length of k value with leading zeros resulting in its truncation. An attacker can obtain the secret key by analyzing both a faulty signature generated by a vulnerable implementation and a correct signature for the same inputs.

Note:

There is a distinct but related issue CVE-2024-48948.

Remediation

There is no fixed version for elliptic.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: archiver@4.0.2 and browserify@16.5.2

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner archiver@4.0.2 glob@7.2.3 inflight@1.0.6
  • Introduced through: openrunner@computestdev/Openrunner browserify@16.5.2 glob@7.2.3 inflight@1.0.6
  • Introduced through: openrunner@computestdev/Openrunner archiver@4.0.2 archiver-utils@2.1.0 glob@7.2.3 inflight@1.0.6
  • Introduced through: openrunner@computestdev/Openrunner archiver@4.0.2 zip-stream@3.0.1 archiver-utils@2.1.0 glob@7.2.3 inflight@1.0.6

Overview

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.

Exploiting this vulnerability results in crashing the node process or in the application crash.

Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.

To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.

PoC

const inflight = require('inflight');

function testInflight() {
  let i = 0;
  function scheduleNext() {
    let key = `key-${i++}`;
    const callback = () => {
    };
    for (let j = 0; j < 1000000; j++) {
      inflight(key, callback);
    }

    setImmediate(scheduleNext);
  }


  if (i % 100 === 0) {
    console.log(process.memoryUsage());
  }

  scheduleNext();
}

testInflight();

Remediation

There is no fixed version for inflight.

References

medium severity

Incorrect Control Flow Scoping

  • Vulnerable module: @tootallnate/once
  • Introduced through: jsdom@16.7.0

Detailed paths

  • Introduced through: openrunner@computestdev/Openrunner jsdom@16.7.0 http-proxy-agent@4.0.1 @tootallnate/once@1.1.2
    Remediation: Upgrade to jsdom@18.0.0.

Overview

Affected versions of this package are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.

Remediation

Upgrade @tootallnate/once to version 2.0.1, 3.0.1 or higher.

References