Vulnerabilities

2 via 3 paths

Dependencies

233

Source

GitHub

Commit

433329a4

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

high severity

Infinite loop

  • Vulnerable module: markdown-it
  • Introduced through: @google-cloud/logging-min@10.4.0

Detailed paths

  • Introduced through: @google-cloud/profiler@GoogleCloudPlatform/cloud-profiler-nodejs#433329a47cd5da1dca602808c658e2c45d466ad1 @google-cloud/logging-min@10.4.0 google-gax@3.6.1 protobufjs-cli@1.1.1 jsdoc@4.0.2 markdown-it@12.3.2

Overview

markdown-it is a modern pluggable markdown parser.

Affected versions of this package are vulnerable to Infinite loop in linkify inline rule when using malformed input.

Remediation

Upgrade markdown-it to version 13.0.2 or higher.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: @google-cloud/logging-min@10.4.0 and pprof@4.0.0

Detailed paths

  • Introduced through: @google-cloud/profiler@GoogleCloudPlatform/cloud-profiler-nodejs#433329a47cd5da1dca602808c658e2c45d466ad1 @google-cloud/logging-min@10.4.0 google-gax@3.6.1 protobufjs-cli@1.1.1 glob@8.1.0 inflight@1.0.6
  • Introduced through: @google-cloud/profiler@GoogleCloudPlatform/cloud-profiler-nodejs#433329a47cd5da1dca602808c658e2c45d466ad1 pprof@4.0.0 @mapbox/node-pre-gyp@1.0.11 rimraf@3.0.2 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