-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Sanitize content to avoid XSS #60
Comments
Markdown Preview Plus use library marked to render html. I think sanitize option can resolve the issue. |
Thanks for pointing this issue. I have changed the marked option by adding I want to make sure that MathJax is still working. But there is something that I don't understand:
I have make sure that in both cases the option |
Ok. I got it: MathJax seems to work only if the auto-reload option is checked. That was the difference between the store version (auto-reload was enabled) and my local version (auto-reload disabled). Pretty strange. |
The problem of enabling the Everything else seems fine. |
Also, |
Thank you for notify on with this issue. I will push a new version soon. |
MathJax is really a problem if we change sanitize to true. I think we can resolve part of this issue -- when mathjax is enabled, change sanitize to false. |
CVE-2017-11593 is attributed to this issue. |
Thanks for let me know it |
Markdown Preview Plus makes Chrome/Chromium vulnerable to XSS attacks on files that are not designed to be interpreted by web applications.
How to reproduce
<script>alert(0)</script>
This behavior makes all users of Markdown Preview Plus vulnerable to XSS attacks in a lot of web sites, because these websites are not designed to escape or force the download of txt files.
How to fix
Markdown Preview Plus should sanitize the content in order to avoid XSS.
The text was updated successfully, but these errors were encountered: