We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In absence of a security policy I am creating the issue here. CVE-2020-28499 https://nvd.nist.gov/vuln/detail/CVE-2020-28499#match-6281551
The text was updated successfully, but these errors were encountered:
@ekelvin what does the library need to avoid Prototype Pollution completely? this?:
- if (key === '__proto__' || key === 'constructor' || key === 'prototype') + if (key === '__proto__' || key === 'constructor' || key === 'prototype' || key === 'toString' || key === 'hasOwnProperty')
Sorry, something went wrong.
Hi @matheo, can you publish your repository in npm registry?
Otherwise, there is this other vulnerability: CVE-2021-23397 (https://nvd.nist.gov/vuln/detail/CVE-2021-23397).
Although I know this vulnerability is about another library but that came up running the dependency check over this merge library!
I don't know if this fix solves the problem
The CVE (GHSA-7wpw-2hjm-89gp) says:
What is the problem?
No branches or pull requests
In absence of a security policy I am creating the issue here.
CVE-2020-28499
https://nvd.nist.gov/vuln/detail/CVE-2020-28499#match-6281551
The text was updated successfully, but these errors were encountered: