π‘οΈ Sentinel: Fix insecure webhook signature generation - #4
π‘οΈ Sentinel: Fix insecure webhook signature generation#4Pmaster-dev wants to merge 2 commits into
Conversation
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
|
π Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a π emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
π¨ Severity: HIGH
π‘ Vulnerability: Webhook payloads were using base64 string encoding for the X-Webhook-Signature header rather than a cryptographic HMAC signature, allowing third parties to forge or tamper with webhook signatures.
π― Impact: Attackers could forge valid-looking webhook signatures or modify payload content in transit.
π§ Fix: Replaced base64 pseudo-signature with an HMAC-SHA256 signature generated over the timestamp and payload using crypto.createHmac and WEBHOOK_SECRET / SESSION_SECRET.
β Verification: Tested signature generation using Node.js crypto via tsx and verified output format t=,v1=.
PR created automatically by Jules for task 16997198982599385288 started by @Pmaster-dev