-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Prototype Pollution #44
Comments
@msrkp thanks for the issue. Will be fixed soon. |
Is there an update on when this will be fixed? |
Fixed in my local, doing some cleanup and deps upgrade. Will get this in soon |
Thank you, @bigopon! Your hard work is greatly appreciated! Do you know when the next release will be? |
@tylerdotson probably in a few days. I'll work with @EisenbergEffect to do a release for this. |
@bigopon the fix can be bypassed with |
@msrkp thanks for catching that! It's fixed in the latest commit. |
Hi @bigopon, |
Hi @msrkp, the advisory has been created GHSA-3c9c-2p65-qvwv |
Hi @bigopon , Awesome, thanks.
More details are available here https://docs.github.com/en/code-security/security-advisories/publishing-a-security-advisory Thanks and Regards, |
That is also done. I wasn't sure whether it's needed after creating the advisory. Thanks for the reply. |
Hello, It is still not fix in live host |
Thanks @mukundbhuva . The site code needs to be rebuilt. Will do so. |
I'm submitting a bug report
parseQueryString of aurelia path is vulnerable to prototype pollution.
POC
aurelia blog is using parseQueryString to parse location.search, so it is vulnerable to prototype pollution
The text was updated successfully, but these errors were encountered: