Failed payment recorded has completed in silverstripe/silverstripe-omnipay
silverstripe-omnipay
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/silverstripe-omnipay Packagist |
|
|
silverstripe-omnipay
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/silverstripe-omnipay Packagist |
|
|
silverstripe-omnipay is a SilverStripe integration with Omnipay PHP payments library. For a subset of Omnipay gateways (those that use intermediary states like `isNotification()` or `isRedirect()`), if the payment identifier or success URL is exposed it is possible for payments to be prematurely marked as completed without payment being taken. This is mitigated by the fact that most payment gateways hide this information from users, however some issuing banks offer flawed 3DSecure implementations that may inadvertently expose this data. The following versions have been patched to fix this issue: `2.5.2`, `3.0.2`, `3.1.4`, and `3.2.1`. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
silverstripe-omnipay is vulnerable when used with Omnipay gateways that use intermediary states such as `isNotification()` or `isRedirect()`. If a payment identifier or success URL is exposed, an attacker can cause a payment to be marked complete before payment is taken. Most gateways hide this information, but some flawed 3DSecure implementations may expose it.
Check installations using Packagist package silverstripe/silverstripe-omnipay in versions below 2.5.2, 3.0.0 to below 3.0.2, 3.1.0 to below 3.1.4, or 3.2.0 to below 3.2.1.