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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Fix for Prototype Pollution - huntr.dev #1088

Merged
merged 3 commits into from
Nov 4, 2020

Conversation

huntr-helper
Copy link
Contributor

https://huntr.dev/users/ljharb has fixed the Prototype Pollution vulnerability 🔨. ljharb has been awarded $25 for fixing the vulnerability through the huntr bug bounty program 💵. 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#2
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/yup/1/README.md

User Comments:

📊 Metadata *

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

⚙️ Description *

This uses a null object as the base locale data, so it doesn't have a prototype to pollute.

💻 Technical 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.

🐛 Proof of Concept (PoC) *

See tests.

🔥 Proof of Fix (PoF) *

See tests.

👍 User Acceptance Testing (UAT)

See tests. I also fixed the overarching test suite, which was only running a single test.

@JamieSlome
Copy link
Contributor

@jquense - referencing our conversation from earlier (418sec/huntr#826).

Let me know if you have any questions! 🍰

@JamieSlome
Copy link
Contributor

@jquense - just a heads up that it seemed as though only one unit test was running previously?

@jquense jquense merged commit 15a0f43 into jquense:master Nov 4, 2020
@jquense
Copy link
Owner

jquense commented Nov 4, 2020

thanks

@JamieSlome
Copy link
Contributor

JamieSlome commented Nov 4, 2020

@jquense - thanks for the swift response and thanks @ljharb / @m0hanlal for the fix/disclosure! 🍰

@alexandernst
Copy link

@jquense can we get a release containing this? (and maybe #1021 ) pretty please?

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.

5 participants