silverstripe/silverstripe-omnipay
Affected
- introduced
0, fixed2.5.2(ecosystem)
Fixed versions
2.5.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2022-29254
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.1Workarounds
There are no known workarounds for this vulnerability.
References
N/A.
For more information
If you have any questions or comments about this advisory:
Low Basis: The source's own band: LOW
0, fixed 2.5.2 (ecosystem)2.5.2
The export has no generic command for this ecosystem.
3.0.0, fixed 3.0.2 (ecosystem)3.0.2
The export has no generic command for this ecosystem.
3.1.0, fixed 3.1.4 (ecosystem)3.1.4
The export has no generic command for this ecosystem.
3.2.0, fixed 3.2.1 (ecosystem)3.2.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0