Vulnerabilities

 2 via 6 paths

Dependencies

 450

Source

 GitHub

Find, fix and prevent vulnerabilities in your code.

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

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: @opentelemetry/core
  • Introduced through: @ministryofjustice/hmpps-digital-prison-reporting-frontend@4.32.1 and applicationinsights@2.9.8

Detailed paths

  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › @ministryofjustice/hmpps-digital-prison-reporting-frontend@4.32.1 › @sentry/node@10.34.0 › @opentelemetry/instrumentation-http@0.208.0 › @opentelemetry/core@2.2.0
  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › applicationinsights@2.9.8 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to applicationinsights@3.8.0.
  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › applicationinsights@2.9.8 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to applicationinsights@3.8.0.
  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › applicationinsights@2.9.8 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/resources@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to applicationinsights@3.8.0.

Overview

@opentelemetry/core is an OpenTelemetry Core provides constants and utilities shared by all OpenTelemetry SDK packages.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the extract function. An attacker can cause excessive memory allocation by sending oversized baggage HTTP headers or equivalent data via non-HTTP transports.

Note: This is only exploitable if the deployment does not enforce transport-layer header size limits, such as when using custom transports or when default HTTP header size limits are increased.

Workaround

This vulnerability can be mitigated by configuring strict header size limits at the server or gateway level, or by validating input size before passing it to the propagator in non-HTTP transports.

Remediation

Upgrade @opentelemetry/core to version 2.8.0 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: bunyan@1.8.15 and @ministryofjustice/hmpps-digital-prison-reporting-frontend@4.32.1

Detailed paths

  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › bunyan@1.8.15 › mv@2.1.1 › rimraf@2.4.5 › glob@6.0.4 › inflight@1.0.6
  • Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › @ministryofjustice/hmpps-digital-prison-reporting-frontend@4.32.1 › 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

Missing Release of Resource after Effective Lifetime vulnerability report