Fix Insecure Webhooks in Polka
Webhooks are trust-based triggers. Without cryptographic signature verification, your Polka endpoint is a public playground for spoofing and unauthorized state changes. If you aren't validating the HMAC, you're effectively leaving your back door wide open for any attacker who finds the URL. Here is how to lock it down using Node's crypto module.
The Vulnerable Pattern
const polka = require('polka'); const { json } = require('body-parser');
polka() .use(json()) .post(‘/api/webhook’, (req, res) => { // VULNERABLE: No signature check. // Anyone can POST a malicious payload here. const { event, data } = req.body; console.log(Processing ${event} for ${data.id}); res.end(‘Success’); }) .listen(3000);
The Secure Implementation
The fix involves implementing a middleware that validates the 'x-hub-signature-256' header (standard for GitHub/Stripe/etc). We generate an HMAC using the SHA-256 algorithm and a shared secret. We then compare our generated hash with the one provided in the request header. Crucially, we use 'crypto.timingSafeEqual' to compare the buffers; this prevents timing attacks that could allow an attacker to guess the signature byte-by-byte by measuring response times.
const polka = require('polka'); const crypto = require('crypto'); const { json } = require('body-parser');const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;
const verifyWebhook = (req, res, next) => { const signature = req.headers[‘x-hub-signature-256’]; if (!signature) return (res.statusCode = 401, res.end(‘Missing Signature’));
const hmac = crypto.createHmac(‘sha256’, WEBHOOK_SECRET); // Note: Use raw body if possible to ensure hash integrity const digest = Buffer.from(‘sha256=’ + hmac.update(JSON.stringify(req.body)).digest(‘hex’), ‘utf8’); const checksum = Buffer.from(signature, ‘utf8’);
if (checksum.length !== digest.length || !crypto.timingSafeEqual(digest, checksum)) { return (res.statusCode = 401, res.end(‘Invalid Signature’)); } next(); };
polka() .use(json()) .post(‘/api/webhook’, verifyWebhook, (req, res) => { res.end(‘Verified and Secure’); }) .listen(3000);
Your Polka API
might be exposed to Insecure Webhooks
74% of Polka apps fail this check. Hackers use automated scanners to find this specific flaw. Check your codebase before they do.
Free Tier • No Credit Card • Instant Report
Verified by Ghost Labs Security Team
This content is continuously validated by our automated security engine and reviewed by our research team. Ghost Labs analyzes over 500+ vulnerability patterns across 40+ frameworks to provide up-to-date remediation strategies.