Vulnerabilities

2 via 4 paths

Dependencies

177

Source

GitHub

Commit

b9c9cb88

Find, fix and prevent vulnerabilities in your code.

Severity
  • 2
Status
  • 2
  • 0
  • 0

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: bunyan@1.8.15

Detailed paths

  • Introduced through: soajs.core.modules@soajs/soajs.core.modules#b9c9cb8840438b60b3b0b436e679dd4ceaba01c5 bunyan@1.8.15 mv@2.1.1 rimraf@2.4.5 glob@6.0.4 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
new

Incorrect Control Flow Scoping

  • Vulnerable module: @tootallnate/once
  • Introduced through: @google-cloud/logging-bunyan@5.1.0

Detailed paths

  • Introduced through: soajs.core.modules@soajs/soajs.core.modules#b9c9cb8840438b60b3b0b436e679dd4ceaba01c5 @google-cloud/logging-bunyan@5.1.0 @google-cloud/logging@11.2.1 @google-cloud/common@5.0.2 teeny-request@9.0.0 http-proxy-agent@5.0.0 @tootallnate/once@2.0.0
  • Introduced through: soajs.core.modules@soajs/soajs.core.modules#b9c9cb8840438b60b3b0b436e679dd4ceaba01c5 @google-cloud/logging-bunyan@5.1.0 @google-cloud/logging@11.2.1 @google-cloud/common@5.0.2 retry-request@7.0.2 teeny-request@9.0.0 http-proxy-agent@5.0.0 @tootallnate/once@2.0.0
  • Introduced through: soajs.core.modules@soajs/soajs.core.modules#b9c9cb8840438b60b3b0b436e679dd4ceaba01c5 @google-cloud/logging-bunyan@5.1.0 @google-cloud/logging@11.2.1 google-gax@4.6.1 retry-request@7.0.2 teeny-request@9.0.0 http-proxy-agent@5.0.0 @tootallnate/once@2.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 3.0.1 or higher.

References