CVE-2021-25946

Overview

Prototype pollution vulnerability in `nconf-toml` versions 0.0.1 through 0.0.2 allows an attacker to cause a denial of service and may lead to remote code execution.

Details

The NPM module `nconf-toml` can be abused by Prototype Pollution vulnerability since the module does not check for the type of object before assigning value to the property. Due to this flaw an attacker could create a non-existent property or be able to manipulate the property which leads to Denial of Service or potentially Remote code execution.

PoC Details

The `nconf-toml` accepts `.toml` properties file without any validations on the values passed into the `toml` properties, by taking this as an advantage an attacker can supply a malicious value by adjusting the `toml` property file to include the `__proto__` property. Since there is no validation before assigning the property to check whether the assigned argument is the Object's own property or not, the property `polluted` will be directly assigned to the new object thereby polluting the Object prototype. Later in the code, if there is a check to validate `polluted` the value would be substituted as "Yes! It's Polluted" as it had been polluted.

PoC Code

var nt = require("nconf-toml")

var fs = require('fs')

var obj = {};

console.log("Before : " + {}.polluted);

var parsed = nt.parse(fs.readFileSync('./Payload.toml', 'utf-8'));

console.log("After : " + {}.polluted);

Affected Environments

0.0.1 to 0.0.2

Remediation

There are a couple of ways to mitigate prototype pollution vulnerabilities, for example: Most of the cases can be solved by freezing an object which doesn’t allow to add, remove, or change its properties. Validating the JSON input with shcema validation, this guarantees that the JSON input contains only predefined attributes. We can change the objects so they won’t have any prototype association by using “Object.create”.

Prevention

No Fix