Vulnerabilities

4 via 5 paths

Dependencies

39

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 3
Status
  • 4
  • 0
  • 0

high severity
new

Inefficient Algorithmic Complexity

  • Vulnerable module: brace-expansion
  • Introduced through: glob@7.2.3

Detailed paths

  • Introduced through: atom-coverage@cgalvarez/atom-coverage glob@7.2.3 minimatch@3.1.5 brace-expansion@1.1.16
    Remediation: Upgrade to glob@10.0.0.

Overview

brace-expansion is a Brace expansion as known from sh/bash

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the expand function. An attacker can cause excessive CPU consumption and block the event loop by supplying a specially crafted string containing multiple consecutive non-expanding '{}' brace groups. The max option does not prevent this issue, as it only limits the output size and not the computational workload.

Remediation

Upgrade brace-expansion to version 5.0.7 or higher.

References

medium severity
new

Uncaught Exception

  • Vulnerable module: joi
  • Introduced through: joi@13.7.0

Detailed paths

  • Introduced through: atom-coverage@cgalvarez/atom-coverage joi@13.7.0
    Remediation: Upgrade to joi@17.13.4.

Overview

Affected versions of this package are vulnerable to Uncaught Exception through the link validation. An attacker can cause the application to crash or become unresponsive by submitting deeply nested input that triggers an unhandled RangeError exception. This is only exploitable if input validation is performed without proper exception handling (such as missing try/catch blocks).

Remediation

Upgrade joi to version 17.13.4, 18.2.1 or higher.

References

medium severity
new

Inefficient Algorithmic Complexity

  • Vulnerable module: js-yaml
  • Introduced through: js-yaml@3.15.0 and cosmiconfig@5.2.1

Detailed paths

  • Introduced through: atom-coverage@cgalvarez/atom-coverage js-yaml@3.15.0
    Remediation: Upgrade to js-yaml@4.2.0.
  • Introduced through: atom-coverage@cgalvarez/atom-coverage cosmiconfig@5.2.1 js-yaml@3.15.0
    Remediation: Upgrade to cosmiconfig@6.0.0.

Overview

js-yaml is a human-friendly data serialization language.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in the storeMappingPair() function in loader.js when handling repeated aliases in merge sequences. An attacker can exhaust CPU resources and significantly degrade service availability by submitting malicious YAML documents.

Remediation

Upgrade js-yaml to version 4.2.0 or higher.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: glob@7.2.3

Detailed paths

  • Introduced through: atom-coverage@cgalvarez/atom-coverage 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