fix(webhooks): validate Twilio signatures with escaped and unescaped query string values fixes #1059 #1061
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.
Fixes #1059
Update the
validateRequest()
function to fallback to a query string parser that does not escape single quotes if the request validation fails.Why?
Query string values that contain single quotes (
'
) are escaped when usingnew URL()
, but the Twilio server seems to generate the signature with the unescaped single quote value, causing the validation to fail in the scenario described in #1059Checklist
If you have questions, please file a support ticket, or create a GitHub Issue in this repository.