razorpay / razorpay/razorpay-node
Possible timing attack in webhook signature verification method
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 243
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
I think below code is susceptible to a timing attack.
https://github.com/razorpay/razorpay-node/blob/92fe1ceb9300eae630824e4618f640fe7d6e6c0c/lib/utils/razorpay-utils.js#L102
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing lib/utils/razorpay-utils.js at the linked line and the surrounding webhook signature verification flow. Check whether existing tests cover this verification path; done means the suspected timing weakness is addressed and regression coverage confirms signature verification still behaves correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100