Vulnerabilities

 3 via 3 paths

Dependencies

 256

Source

 GitHub

Commit

 6e7197d2

Find, fix and prevent vulnerabilities in your code.

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

medium severity
new

Prototype Pollution

  • Vulnerable module: express
  • Introduced through: @nestjs/platform-express@11.1.5

Detailed paths

  • Introduced through: prime-nestjs@josephgoksu/prime-nestjs#6e7197d2546e0bbacb79e9ad43c6e92b6e430f5c › @nestjs/platform-express@11.1.5 › express@5.1.0

Overview

express is a minimalist web framework.

Affected versions of this package are vulnerable to Prototype Pollution in the request.query object. An attacker can modify inherited object prototype properties by supplying query string parameters that match prototype property names.

This is only exploitable if the extended query parser is enabled. This is the default in 4.x versions but must be configured in 5.x, such as with 'query parser': 'extended'.

Workaround

This vulnerability can be mitigated by providing qs directly and specifying plainObjects: true when parsing query strings.

Remediation

Upgrade express to version 4.22.0, 5.2.0 or higher.

References

Prototype Pollution vulnerability report

medium severity
new

Prototype Pollution

  • Vulnerable module: js-yaml
  • Introduced through: @nestjs/swagger@11.2.0

Detailed paths

  • Introduced through: prime-nestjs@josephgoksu/prime-nestjs#6e7197d2546e0bbacb79e9ad43c6e92b6e430f5c › @nestjs/swagger@11.2.0 › js-yaml@4.1.0
    Remediation: Upgrade to @nestjs/swagger@11.2.2.

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution via the merge function. An attacker can alter object prototypes by supplying specially crafted YAML documents containing __proto__ properties. This can lead to unexpected behavior or security issues in applications that process untrusted YAML input.

Workaround

This vulnerability can be mitigated by running the server with node --disable-proto=delete or by using Deno, which has pollution protection enabled by default.

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade js-yaml to version 3.14.2, 4.1.1 or higher.

References

Prototype Pollution vulnerability report

medium severity

SQL Injection

  • Vulnerable module: typeorm
  • Introduced through: typeorm@0.3.25

Detailed paths

  • Introduced through: prime-nestjs@josephgoksu/prime-nestjs#6e7197d2546e0bbacb79e9ad43c6e92b6e430f5c › typeorm@0.3.25
    Remediation: Upgrade to typeorm@0.3.26.

Overview

typeorm is an ORM that can run in NodeJS, Browser, Cordova, PhoneGap, Ionic, React Native, NativeScript, Expo, and Electron platforms and can be used with TypeScript and JavaScript (ES5, ES6, ES7, ES8).

Affected versions of this package are vulnerable to SQL Injection via the repository.save or repository.update features when processing crafted input, due to improper handling in the sqlstring call with stringifyObjects set to false. An attacker can execute arbitrary SQL commands to bypass field-level update restrictions for columns such as user roles, by supplying specially crafted nested JSON.

Remediation

Upgrade typeorm to version 0.3.26 or higher.

References

SQL Injection vulnerability report