CyberRota Analysis
AI-GeneratedThe vulnerability affects the Pay payments engine for Ruby on Rails versions 6.0 and higher, specifically in the signature validation process of the PaddleBillingController. An unauthenticated remote attacker can exploit this flaw to forge accepted webhooks, potentially allowing unauthorized changes to billing states, provisioning of paid features, and triggering of customer notifications. Organizations using affected versions should prioritize upgrading to version 11.6.2 to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.