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

Prevent exploitation of CVE-2021-23440 #38

Closed
wants to merge 1 commit into from

Conversation

Jacc0
Copy link

@Jacc0 Jacc0 commented Oct 7, 2021

Hi @jonschlinkert , we are urgently looking for a patch for version 2.0.1 to intergrade into Angular
Reading the POC I think this solution might prevent exploitation.

Do you have time to review/test?

Hi @jonschlinkert , we are urgently looking for a patch for version 2.0.1 to intergrade into Angular
Reading the POC I think this solution might prevent exploitation.

Do you have time to review/test?
@Jacc0 Jacc0 changed the title Update index.js Prevent exploitation of CVE-2021-23440 Oct 7, 2021
@wejendorp
Copy link

Testing out the PoC from the report, v2.0.1 does not seem to be vulnerable.

git checkout 2.0.0
rm -rf node_modules package-lock.json && npm i && node poc.js

AssertionError [ERR_ASSERTION]: 'Yes! Its Polluted' == undefined
git checkout 2.0.1
rm -rf node_modules package-lock.json && npm i && node poc.js

No error

@shashi4a6
Copy link

Testing out the PoC from the report, v2.0.1 does not seem to be vulnerable.

git checkout 2.0.0
rm -rf node_modules package-lock.json && npm i && node poc.js

AssertionError [ERR_ASSERTION]: 'Yes! Its Polluted' == undefined
git checkout 2.0.1
rm -rf node_modules package-lock.json && npm i && node poc.js

No error

Hi, I am currently working on to fix the vulnerability reported for version 2.0.1. Do you mean the current version 2.0.1 is not vulnerable and no need to update to new version. If not, can you please let me know when can we have a patch available for this.

@jonschlinkert
Copy link
Owner

Sorry for the late reply. I think @wejendorp is correct, I'm fairly certain this was resolved. Can you provide a failing unit test to demonstrate where the vulnerability persists?

@Jacc0
Copy link
Author

Jacc0 commented Apr 6, 2022

I'll accept your analysis to be correct

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.

4 participants