Vulnerabilities |
4 via 10 paths |
|---|---|
Dependencies |
451 |
Source |
GitHub |
Find, fix and prevent vulnerabilities in your code.
high severity
- 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.1Remediation: 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.1Remediation: 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.1Remediation: 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
medium severity
new
- Vulnerable module: qs
- Introduced through: express@4.22.2
Detailed paths
-
Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › express@4.22.2 › qs@6.15.3Remediation: Upgrade to express@5.1.0.
-
Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › express@4.22.2 › body-parser@1.20.6 › qs@6.15.3Remediation: Upgrade to express@5.0.0.
Overview
qs is a querystring parser that supports nesting and arrays, with a depth limit.
Affected versions of this package are vulnerable to Uncaught Exception in the isBuffer() function in lib/utils.js, which calls obj.constructor.isBuffer(obj) without checking that it is callable, reached from stringify() at lib/stringify.js:127. An attacker can throw an uncaught TypeError that fails each request with HTTP 500, and terminates the worker process when stringify() runs in an unguarded async context, by supplying a query string such as x[constructor][isBuffer]=y that sets constructor.isBuffer to a non-function value. This requires the application to call qs.parse() with plainObjects: true or allowPrototypes: true, which preserves the constructor own property, and to then pass the parsed result to qs.stringify().
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
wspackage
Remediation
Upgrade qs to version 6.16.0 or higher.
References
medium severity
new
- Vulnerable module: qs
- Introduced through: express@4.22.2
Detailed paths
-
Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › express@4.22.2 › qs@6.15.3Remediation: Upgrade to express@5.1.0.
-
Introduced through: hmpps-welcome-people-into-prison-ui@ministryofjustice/hmpps-welcome-people-into-prison-ui › express@4.22.2 › body-parser@1.20.6 › qs@6.15.3Remediation: Upgrade to express@5.0.0.
Overview
qs is a querystring parser that supports nesting and arrays, with a depth limit.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the parseArrayValue() comma-parsing logic, which applies the arrayLimit and throwOnLimitExceeded checks only to flat values, so a bracket-key input such as a[]=1,2,3,4 is treated as non-flat and its comma-split inner array is wrapped after parsing without ever being length-checked. An attacker can exceed the configured array limit and force excessive memory allocation by supplying a query string or form body that uses the bracket-key comma form, for example a[]=1,2,3,.... This requires the application to parse untrusted input with the comma: true option enabled alongside a configured arrayLimit or throwOnLimitExceeded.
PoC
const qs = require('qs')
const options = { comma: true, arrayLimit: 3, throwOnLimitExceeded: true }
const result = qs.parse('a[]=1,2,3,4', options)
console.log(result.a[0].length) // 4; expected RangeError
const big = qs.parse('a[]=' + '1,'.repeat(1000000) + '1', { comma: true, arrayLimit: 20 })
console.log(big.a[0].length) // 1000001
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
wspackage
Remediation
Upgrade qs to version 6.16.0 or higher.
References
medium severity
- 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.