Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

Fixed Prototype Pollution bug on smart-extend #1

Merged
merged 1 commit into from
Sep 7, 2020

Conversation

Asjidkalam
Copy link

@Asjidkalam Asjidkalam commented Sep 4, 2020

馃搳 Metadata *

Prototype Pollution bug

Bounty URL: https://www.huntr.dev/bounties/1-npm-smart-extend

鈿欙笍 Description *

smart-extend is an extension to jQuery's classic extend() method with additional features providing you with more power and control over your object extensions/clones.

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.

馃捇 Technical Description *

The bug is fixed by validating the input key to check for prototypes. It is implemented by a simple validation to check for prototype keywords (__proto__, constructor and prototype), where if it exists, the function returns the object without modifying it, thus fixing the Prototype Pollution Vulnerability.

馃悰 Proof of Concept (PoC) *

Clone the project, install the required dependencies and on running the below snippet of code, it triggers prototype pollution and logs pwned!.

var extend = require('smart-extend');
var payload = '{"__proto__":{"polluted":"pwned!"}}';
var test = {};
extend.deep({},JSON.parse(payload));
console.log(test.polluted);

image

馃敟 Proof of Fix (PoF) *

After the fix is applied, it returns an error since the polluted referred in the PoC is no more accessible(which is intended). Hence fixing the issue.

image

馃憤 User Acceptance Testing (UAT)

Just prevented some keywords as key and no breaking changes are introduced. :)

Copy link

@mufeedvh mufeedvh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean Fix! 馃憦馃帀

LGTM

@JamieSlome JamieSlome merged commit 8b88bc5 into 418sec:master Sep 7, 2020
@huntr-helper
Copy link
Member

Congratulations Asjidkalam - your fix has been selected! 馃帀

Thanks for being part of the community & helping secure the world's open source code.
If you have any questions, please respond in the comments section. Your bounty is on its way - keep hunting!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants