Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.Test your applications
- Snyk ID SNYK-JS-TINYCONF-598792
- published 1 Sep 2020
- disclosed 17 Aug 2020
- credit Beomjin Lee
How to fix?
There is no fixed version for
tiny-conf is a Node.js configuration with files, environment variables, command-line arguments, ... pluggable architecture in order to work in the browser & server-side
Affected versions of this package are vulnerable to Prototype Pollution via the
const tinyConf = require('tiny-conf'); tinyConf.set('__proto__.polluted', true); console.log(polluted); //true
There are two main ways in which the pollution of prototypes occurs:
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
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object:
Hoek are examples of libraries susceptible to recursive merge attacks.
Property definition by path
theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to
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:
|Denial of service (DoS)||Client||This is the most likely attack.
DoS occurs when
The attacker pollutes
For example: if an attacker pollutes
|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.
|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
The following environments are susceptible to a Prototype Pollution attack:
How to prevent
Freeze the prototype— use
Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)), breaking the prototype chain and preventing pollution.
As a best practice use