cond0r / verify-webhooks-with-middleware Goto Github PK

Thanks very much for this repo as I was building a similar thing. My only question, because I am facing a similar issue, is does this really protect API routes? B/c to get the signature you need to hit the pages/api/signature. This returns the signature, and so obviously this endpoint itself can't be protected. So what prevents somebody from just hitting the signature endpoint, getting a signature and then attaching it to a request to the webhook api? I mean it seems like you can never really protect API's as there is always 1 api route that must be open to generate the signature, it would be trivial to just get around everything by hitting this API route to get the signature. So even if you don't have access to the Secret itself, who cares. You can just generate the signature and access all the protected API routes. how do you solve this basic problem?