[Security] SECVULN-8621: Fix XSS Vulnerability where content-type header wasn't explicitly set in API requests #21930
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.
Description
ensureContentTypeHeader
middleware to set the responseContent-Type
to match the type of content that the server will process.SOLUTION
ensureContentTypeHeader
middleware is used to determine if the content-type set in the API request is the expected content type. If it's not a match:NOTE: The same function is used in
doRequest
function which is used in processing CLI requests to the Consul API.Testing & Reproduction steps
Updated unit tests to add additional checks for content-type header
Vercel should deploy UI with no errors
PR Checklist