@chix/flow@1.15.4

Vulnerabilities

2 via 2 paths

Dependencies

14

Source

npm

Find, fix and prevent vulnerabilities in your code.

Severity
  • 2
Status
  • 2
  • 0
  • 0

high severity

Arbitrary Code Execution

  • Vulnerable module: json-ptr
  • Introduced through: json-ptr@1.3.2

Detailed paths

  • Introduced through: @chix/flow@1.15.4 json-ptr@1.3.2
    Remediation: Upgrade to json-ptr@2.1.0.

Overview

json-ptr is a complete implementation of JSON Pointer (RFC 6901) for nodejs and modern browsers.

Affected versions of this package are vulnerable to Arbitrary Code Execution via the .get() method.

Remediation

Upgrade json-ptr to version 2.1.0 or higher.

References

high severity

Prototype Pollution

  • Vulnerable module: json-ptr
  • Introduced through: json-ptr@1.3.2

Detailed paths

  • Introduced through: @chix/flow@1.15.4 json-ptr@1.3.2
    Remediation: Upgrade to json-ptr@2.0.0.

Overview

json-ptr is a complete implementation of JSON Pointer (RFC 6901) for nodejs and modern browsers.

Affected versions of this package are vulnerable to Prototype Pollution. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.html#set) when the force flag is set to true.

The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.

PoC

  • install json-ptr module:

  • npm i json-ptr

  • run the following poc.js: ``` const { JsonPointer } = require("json-ptr");

let obj = {}; console.log("Before : " + obj.polluted); // JsonPointer.set({}, '/constructor/prototype/polluted', "yes", true); JsonPointer.set({}, '/proto/polluted', "yes", true); console.log("After : " + obj.polluted);


Observed output:

Before : undefined After : yes


## 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]
<br>  

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. <br>DoS occurs when `Object` holds generic functions that are implicitly called for various operations (for example, `toString` and `valueOf`). <br> 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.  <br>**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.<br>**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.<br>  **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
    

## 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](https://github.com/HoLyVieR/prototype-pollution-nsec18/blob/master/paper/JavaScript_prototype_pollution_attack_in_NodeJS.pdf)

## Remediation
Upgrade `json-ptr` to version 2.0.0 or higher.
## References
- [Vulnerable Code](https://github.com/flitbit/json-ptr/blob/master/src/util.ts#L174)