Pay-rails pay
pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier
Pay is a payments engine for Ruby on Rails 6.0 and higher. Prior to 11.6.2, Pay::Webhooks::PaddleBillingController#valid_signature? in app/controllers/pay/webhooks/paddle_billing_controller.rb compares the computed 64-character SHA-256 HMAC with the attacker-controlled h1 token from the Paddle-Signature header using Ruby String#==. An unauthenticated remote attacker who can repeatedly submit requests to /pay/webhooks/paddle_billing and obtain sufficiently precise timing measurements can infer matching digest prefixes and recover a valid signature. A forged accepted webhook is enqueued through Pay::Webhooks::ProcessJob and can cause a host application to update billing state, provision paid features, record refunds, or trigger customer notifications. This issue is fixed in version 11.6.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 11.6.2
Fixed in 11.6.2
Mitigation
Upgrade pay to 11.6.2 or later.
References
- Vendor advisory github.com/pay-rails/pay/security/advisories/G…
- Patch github.com/pay-rails/pay/commit/ba6494109d8820…
- Release notes github.com/pay-rails/pay/releases/tag/v11.6.2
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.