Security Fix for Prototype Pollution - huntr.dev

[huntr-helper]

https://huntr.dev/users/arjunshibu has fixed the Prototype Pollution vulnerability 🔨. Think you could fix a vulnerability like this?

Get involved at https://huntr.dev/

Q | A
Version Affected | ALL
Bug Fix | YES
Original Pull Request | 418sec#1
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/@lyngs/digger/1/README.md

User Comments:

📊 Metadata *

@lyngs/digger is vulnerable to Prototype Pollution.

Bounty URL: https://www.huntr.dev/bounties/1-npm-%40lyngs%2Fdigger

⚙️ Description *

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.

💻 Technical Description *

Fix implemented by not allowing to modify object prototype.

🐛 Proof of Concept (PoC) *

1. Create the following PoC file:

// poc.js
var digger = require("@lyngs/digger")
console.log("Before : " + {}.polluted);
digger.digger({}, '__proto__.polluted', 'Yes! Its Polluted', {extend: true})
console.log("After : " + {}.polluted);

2. Execute the following commands in terminal:

npm i @lyngs/digger # Install affected module
node poc.js #  Run the PoC

3. Check the Output:

Before : undefined
After : Yes! Its Polluted

🔥 Proof of Fix (PoF) *

+1 User Acceptance Testing (UAT)

• I've executed unit tests.
• After fix the functionality is unaffected.