CVE-2022-29254: Interpretation Conflict
(updated )
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.
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
- nvd.nist.gov/vuln/detail/CVE-2022-29254
Detect and mitigate CVE-2022-29254 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 →