You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we currently just save whatever availability string that the client sends into the database.
This poses a XSS risk because we would then send this unsanitized input (from the frontend perspective) from one client to another. In theory, this should be ok if the way that we parse the json string on the frontend is secure, but this poses a risk regardless.
More importantly, we don't want there to be an availability string that is malformed/inconsistent from a bug to be entered without checking into the database.
The text was updated successfully, but these errors were encountered:
Description
I think we currently just save whatever availability string that the client sends into the database.
This poses a XSS risk because we would then send this unsanitized input (from the frontend perspective) from one client to another. In theory, this should be ok if the way that we parse the json string on the frontend is secure, but this poses a risk regardless.
More importantly, we don't want there to be an availability string that is malformed/inconsistent from a bug to be entered without checking into the database.
The text was updated successfully, but these errors were encountered: