Vulnerabilities

 5 via 65 paths

Dependencies

 304

Source

 GitHub

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 5
Status
  • 5
  • 0
  • 0

high severity
new

Denial of Service (DoS)

  • Vulnerable module: multer
  • Introduced through: @nestjs/platform-express@11.2.5, @tresdoce-nestjs-toolkit/http-client@2.0.13 and others

Detailed paths

  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @nestjs/platform-express@11.2.5 › multer@2.2.0
    Remediation: Upgrade to @nestjs/platform-express@12.0.2.
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/http-client@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/health@2.0.14 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/rate-limit@0.2.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via the appendField call in make-middleware.js when processing multipart form field names. An attacker can send a request containing an invalid field name that causes appendField to throw an uncaught exception, crashing the Node.js process. The fix wraps the call in a try/catch and rejects the request with an INVALID_FIELD_NAME error instead of propagating the exception.

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 multer to version 2.3.0 or higher.

References

Denial of Service (DoS) vulnerability report

high severity
new

Denial of Service (DoS)

  • Vulnerable module: multer
  • Introduced through: @nestjs/platform-express@11.2.5, @tresdoce-nestjs-toolkit/http-client@2.0.13 and others

Detailed paths

  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @nestjs/platform-express@11.2.5 › multer@2.2.0
    Remediation: Upgrade to @nestjs/platform-express@12.0.3.
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/http-client@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/health@2.0.14 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/rate-limit@0.2.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via incomplete cleanup of uploaded files when a request is aborted before the storage engine assigns a file path. When an upload is aborted mid-flight, the finishAbort function in make-middleware.js snapshots only the files that already have a path at the moment of abort; any file whose storage engine completes naming and writing after that snapshot is never added to the removal list and is never deleted, leaving orphaned files on disk (or in the configured storage backend). An attacker can repeatedly send and abort multipart upload requests to accumulate unbounded orphaned files, exhausting available disk space.

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 multer to version 2.4.0 or higher.

References

Denial of Service (DoS) vulnerability report

high severity
new

Uncaught Exception

  • Vulnerable module: multer
  • Introduced through: @nestjs/platform-express@11.2.5, @tresdoce-nestjs-toolkit/http-client@2.0.13 and others

Detailed paths

  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @nestjs/platform-express@11.2.5 › multer@2.2.0
    Remediation: Upgrade to @nestjs/platform-express@12.0.2.
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/http-client@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/health@2.0.14 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/rate-limit@0.2.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0

Overview

Affected versions of this package are vulnerable to Uncaught Exception via the appendField call in make-middleware.js when processing multipart form field names. An attacker submitting a malformed or invalid field name in a multipart upload request causes an unhandled exception that crashes the process. The fix wraps the appendField call in a try/catch and aborts with an INVALID_FIELD_NAME error code instead of propagating the exception.

Remediation

Upgrade multer to version 2.3.0 or higher.

References

Uncaught Exception vulnerability report

high severity
new

Race Condition

  • Vulnerable module: multer
  • Introduced through: @nestjs/platform-express@11.2.5, @tresdoce-nestjs-toolkit/http-client@2.0.13 and others

Detailed paths

  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @nestjs/platform-express@11.2.5 › multer@2.2.0
    Remediation: Upgrade to @nestjs/platform-express@12.0.2.
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/http-client@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/health@2.0.14 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/rate-limit@0.2.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0

Overview

Affected versions of this package are vulnerable to Race Condition in the fileFilter parameter. An attacker can upload files exceeding the intended size limit by exploiting a race condition when asynchronous filtering is used together with file size restrictions.

Remediation

Upgrade multer to version 2.3.0 or higher.

References

Race Condition vulnerability report

high severity
new

Denial of Service (DoS)

  • Vulnerable module: multer
  • Introduced through: @nestjs/platform-express@11.2.5, @tresdoce-nestjs-toolkit/http-client@2.0.13 and others

Detailed paths

  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @nestjs/platform-express@11.2.5 › multer@2.2.0
    Remediation: Upgrade to @nestjs/platform-express@12.0.2.
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/http-client@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/health@2.0.14 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/rate-limit@0.2.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/tracing@2.0.13 › @tresdoce-nestjs-toolkit/utils@2.0.13 › @nestjs/platform-express@11.2.5 › multer@2.2.0
  • Introduced through: nestjs-starter@rudemex/nestjs-starter › @tresdoce-nestjs-toolkit/paas@2.0.14 › @tresdoce-nestjs-toolkit/response-parser@2.0.13 › @tresdoce-nestjs-toolkit/filters@2.0.13 › @tresdoce-nestjs-toolkit/core@2.1.0 › @nestjs/platform-express@11.2.5 › multer@2.2.0

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via the diskStorage engine's _handleFile function, which fails to close or destroy the destination write stream when an upload is aborted before it completes. Each aborted request leaks an open file descriptor and retains its disk blocks until the process exits, allowing an attacker to exhaust the process's available file descriptors by repeatedly initiating and aborting multipart file uploads, causing a denial of service.

Note: This is only exploitable when diskStorage is used as the multer storage engine.

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 multer to version 2.3.0 or higher.

References

Denial of Service (DoS) vulnerability report