Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Fix for Prototype Pollution - huntr.dev #270

Merged
merged 2 commits into from Jul 15, 2021

Conversation

huntr-helper
Copy link

https://huntr.dev/users/Asjidkalam 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/mout/1/README.md

User Comments:

馃搳 Metadata *

Prototype Pollution bug

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

鈿欙笍 Description *

mout is vulnerable to Prototype Pollution. This package allowing for modification of prototype behavior, which may result in Information Disclosure/DoS/RCE.

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 props in set 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 Yes! Its Polluted.

var mout = require("mout")
var obj = {}
console.log("Before : " + {}.polluted);
mout.object.set(obj,'__proto__.polluted','Yes! Its Polluted');
console.log("After : " + {}.polluted);

image

馃敟 Proof of Fix (PoF) *

After the fix is applied, it returns undefined 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 p and no breaking changes are introduced. :)

@JamieSlome
Copy link
Contributor

@millermedeiros - let me know if you have any questions or thoughts, cheers! 馃嵃

@ghost
Copy link

ghost commented Feb 18, 2021

Any update for this fix?

@andrew-ignatiev
Copy link

@roboshoes could you merge PR to fix https://snyk.io/vuln/npm:mout

@roboshoes roboshoes merged commit 3fecf13 into mout:master Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants