Vulnerabilities

 2 via 6 paths

Dependencies

 350

Source

 GitHub

Commit

 fdd5eaed

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

high severity

Denial of Service (DoS)

  • Vulnerable module: http-proxy-middleware
  • Introduced through: http-proxy-middleware@0.20.0

Detailed paths

  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › http-proxy-middleware@0.20.0
    Remediation: Upgrade to http-proxy-middleware@2.0.7.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) due to an UnhandledPromiseRejection error thrown by micromatch. An attacker could kill the Node.js process and crash the server by making requests to certain paths.

PoC

  1. Run a server like this:
const express = require('express')
const { createProxyMiddleware } = require('http-proxy-middleware')

const frontend = express()
frontend.use(createProxyMiddleware({
  target: 'http://localhost:3031',
  pathFilter: '*'
}))
frontend.listen(3030)

const backend = express()
backend.use((req, res) => res.send('ok'))
backend.listen(3031)
  1. curl 'localhost:3030//x@x'

Expected: Response with payload ok

Actual: Server crashes with error TypeError: Expected input to be a string (from micromatch)

On v1 and v2 of http-proxy-middleware, it's also possible to exclude pathFilter and cause the server to crash with TypeError: Cannot read properties of null (reading 'indexOf') (from matchSingleStringPath).

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 http-proxy-middleware to version 2.0.7, 3.0.3 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: nyc@15.1.0

Detailed paths

  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › nyc@15.1.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › nyc@15.1.0 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › nyc@15.1.0 › test-exclude@6.0.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › nyc@15.1.0 › istanbul-lib-processinfo@2.0.3 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: ccd-api-gateway-web@hmcts/ccd-api-gateway#fdd5eaedb45abba376060e30233d41014575ed95 › nyc@15.1.0 › spawn-wrap@2.0.0 › 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

Missing Release of Resource after Effective Lifetime vulnerability report