-
-
Notifications
You must be signed in to change notification settings - Fork 324
Add warning for html.script
#924
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
Comments
Can you assign me the task? Will be a good starting point. |
We don't utilize the issue assignment feature on GitHub. The first person to open a draft PR gets priority to resolve it. |
ok thanks! will do that. |
@Archmonger, was your intention for this to be in the docstring. |
Yeah, since the docstring gets turned into auto-docs. |
hey! can you please tell me where do i have to put or write the documention i mean in which file? |
@Archmonger, can we create a follow-up ticket for a tool that would sanitize inputs to scripts? I think we can do more to help mitigate this risk for users. |
You think this could be added to our flake8 plugin? |
It's possible, but if that's all we supplied users might improperly sanitize inputs. Better to provide a standardized solution. |
That might be a bit over engineered for a tag that we shouldn't incentivize using. In my opinion, due to script tags being inherently dangerous we should treat them similar to React It's best to get the idea into user's heads that "you can use this but it's risky so you probably shouldn't." |
I like that idea. We could require the script to be passed as a kwarg with a scary name like |
Current Situation
Currently, there is no documented warnings for the potential of XSS attacks when using
html.script
Proposed Actions
We should add a disclaimer to warn users not to use raw user inputs (from any untrusted data source) within the script contents to avoid XSS attacks.
The text was updated successfully, but these errors were encountered: