Harden Xero webhook signature validation#92
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Summary
XERO_WEBHOOK_SIGNING_KEYat runtimerequest->rawBody, matching webhook HMAC expectationshash_equals()and fail closed with framework 401 responses instead of echo/die output/claim #55
Verification
tests/check-xero-webhook-signature-hardening.shgit diff --checkphp -l admin/modules/v1/controllers/XeroWebhookController.phpcould not be run locally because this environment does not havephpinstalledScope
This is a narrow Xero webhook signing-key validation slice. It does not touch Xero OAuth client-secret config already covered by other PRs, AWS/IAM/S3, Civil ID flows, OneSignal, service tokens, live Xero access, or real private signing-key values.
Transparency: AI-assisted with OpenAI Codex; I reviewed the diff and verification before submitting.