Repository navigation
fix(security): use constant-time comparison for webhook signature validation [closes #479] #495
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
Open
gopi-701
wants to merge
7
commits into
razorpay:master
Choose a base branch
from
gopi-701:fix/timing-attack-webhook-signature
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
3c5f718
fix(security): use constant-time comparison for webhook signature val…
gopi-701 d9c5360
fix(customers): allow string '0'/'1' for fail_existing in types
gopi-701 1d8860e
fix(security): use constant-time comparison for webhook signature val…
gopi-701 33c1dcb
fix(security): use constant-time comparison for webhook signature val…
gopi-701 e4a3424
fix(security): use constant-time comparison for webhook signature val…
gopi-701 5e4512d
test: make timing-safe webhook signature tests top-level
gopi-701 ed61e1d
fix(security): use constant-time string comparison for webhook signat…
gopi-701 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two
it(...)blocks are inside the callback of the existingit('validateWebhookSignature', ...), because that test's closing});was moved down to line 136. Mocha doesn't run anitregistered from inside a running test: it gets added to the root suite after that suite has already run, and nothing reports it. I checked this with mocha 9: an outer test containing two failing innerits passes, and the inner tests never show up in the spec reporter. So the 379 passing tests don't include either of the new ones.Fix: close the existing test after its
assert.ok(...)(line 107), then remove the extra});at line 136. Also, the first new test is the same as the existing one with a different wrong signature, so it doesn't check that a constant-time comparison is used. You could drop it, or spy oncrypto.timingSafeEqualand assert that it gets called.