We found results for “


Date: December 29, 2020


Prototype pollution vulnerability in ‘getobject’ version 0.1.0 allows an attacker to cause a denial of service and may lead to remote code execution.


The NPM module 'getobject' can be abused by Prototype Pollution vulnerability since the function 'set()' did 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 able to manipulate the property which leads to Denial of Service or potentially Remote code execution.

PoC Details

The `set()` function accepts three arguments `obj, parts, value`. Due to the absence of validation, at values passed into `parts, value` arguments, an attacker can supply a malicious value by adjusting the `parts`` value to include the `__proto__` property. Since there is no validation before assigning property to check whether the assigned `parts` is the Object's own property or not, the property `isAdmin` will be directly be assigned to the empty obj({}) thereby polluting the Object prototype. Later in the code, if there is a check to validate `isAdmin` the valued would be substituted as "true" as it had been polluted.

PoC Code

const getObject = require('getobject'); 
var obj = {};
console.log("Before Polluting : " + obj.isAdmin); 
getObject.set(obj, '__proto__.isAdmin', true);
console.log("After Polluting: " + obj.isAdmin);

Affected Environments



Upgrade to version 1.0.0

Language: Java

Good to know:


Upgrade Version

Upgrade to version getobject - 1.0.0

Learn More

Base Score:
Attack Vector (AV):
Attack Complexity (AC):
Privileges Required (PR):
User Interaction (UI):
Scope (S):
Confidentiality (C): Partial
Integrity (I): Partial
Availability (A): Partial
Base Score:
Access Vector (AV):
Access Complexity (AC):
Authentication (AU):
Confidentiality (C): Low
Integrity (I): Low
Availability (A): None
Additional information: