Mitigation for POST requests from malicious forms #1969
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In discussion on gh-1830, I found that HTML forms in Firefox do not send an Origin header. You can therefore submit a POST request with an empty body to trigger certain actions, such as starting a kernel, avoiding the origin check we do.
This mitigates that for creating files and starting kernels, by requiring a JSON body, even if there's no data. I cannot currently find a way to create a JSON body in a request sent from a form.
The other cases I've found are interrupting and restarting kernels. This does not affect those cases, but they are only possible if you have a kernel ID.