Skip to content

Failed payment recorded has completed in Silverstripe Omnipay

Low severity GitHub Reviewed Published Jun 6, 2022 in silverstripe/silverstripe-omnipay • Updated Jan 27, 2023

Package

composer silverstripe/silverstripe-omnipay (Composer)

Affected versions

< 2.5.2
>= 3.0.0, < 3.0.2
>= 3.1.0, < 3.1.4
>= 3.2.0, < 3.2.1

Patched versions

2.5.2
3.0.2
3.1.4
3.2.1

Description

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.2
  • 3.0.2
  • 3.1.4
  • 3.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:

References

Published to the GitHub Advisory Database Jun 6, 2022
Reviewed Jun 6, 2022
Published by the National Vulnerability Database Jun 9, 2022
Last updated Jan 27, 2023

Severity

Low
3.7
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE ID

CVE-2022-29254

GHSA ID

GHSA-48f2-m7jg-866x
Checking history
See something to contribute? Suggest improvements for this vulnerability.