GMS-2022-1827: Duplicate of ./packagist/silverstripe/silverstripe-omnipay/CVE-2022-29254.yml
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
References
- github.com/advisories/GHSA-48f2-m7jg-866x
- github.com/silverstripe/silverstripe-omnipay/commit/7dee9a1e0a5f54c2dc06e018cff3d9a19044e01b
- github.com/silverstripe/silverstripe-omnipay/releases/tag/2.5.2
- github.com/silverstripe/silverstripe-omnipay/releases/tag/3.0.2
- github.com/silverstripe/silverstripe-omnipay/releases/tag/3.1.4
- github.com/silverstripe/silverstripe-omnipay/releases/tag/3.2.1
- github.com/silverstripe/silverstripe-omnipay/security/advisories/GHSA-48f2-m7jg-866x
Code Behaviors & Features
Detect and mitigate GMS-2022-1827 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →