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
As shown in vuejs/vuex-router-sync#89 (comment) and https://codesandbox.io/s/5x2wpo27k4, devalue exposes a XSS vulnerability, when an object key contains unsafe characters.
devalue
From the issue:
I think it should be safe to use the same approach as in serialize-javascript to replace unsafe characters: https://github.com/yahoo/serialize-javascript/blob/35f64803a3a67662e16ad5260901d4e291260989/index.js#L126
The text was updated successfully, but these errors were encountered:
Simpler reproduction:
Server-side (express + query):
Sorry, something went wrong.
Thank you for finding/fixing this — bit embarrassed about how long it went unmerged, but this is now released as 1.1.1
Successfully merging a pull request may close this issue.
As shown in vuejs/vuex-router-sync#89 (comment) and https://codesandbox.io/s/5x2wpo27k4,
devalue
exposes a XSS vulnerability, when an object key contains unsafe characters.From the issue:
The text was updated successfully, but these errors were encountered: