Описание
Failed payment recorded has completed in Silverstripe Omnipay
Impact
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.
Patches
The following versions have been patched to fix this issue:
2.5.23.0.23.1.43.2.1
Workarounds
There are no known workarounds for this vulnerability.
References
N/A.
For more information
If you have any questions or comments about this advisory:
- Email us at security@silverstripe.org
Ссылки
- https://github.com/silverstripe/silverstripe-omnipay/security/advisories/GHSA-48f2-m7jg-866x
- https://nvd.nist.gov/vuln/detail/CVE-2022-29254
- https://github.com/silverstripe/silverstripe-omnipay/commit/7dee9a1e0a5f54c2dc06e018cff3d9a19044e01b
- https://github.com/silverstripe/silverstripe-omnipay/releases/tag/2.5.2
- https://github.com/silverstripe/silverstripe-omnipay/releases/tag/3.0.2
- https://github.com/silverstripe/silverstripe-omnipay/releases/tag/3.1.4
- https://github.com/silverstripe/silverstripe-omnipay/releases/tag/3.2.1
Пакеты
silverstripe/silverstripe-omnipay
< 2.5.2
2.5.2
silverstripe/silverstripe-omnipay
>= 3.0.0, < 3.0.2
3.0.2
silverstripe/silverstripe-omnipay
>= 3.1.0, < 3.1.4
3.1.4
silverstripe/silverstripe-omnipay
>= 3.2.0, < 3.2.1
3.2.1
Связанные уязвимости
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.