Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-48f2-m7jg-866x: 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.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:

ghsa
#vulnerability#git

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

  • GHSA-48f2-m7jg-866x
  • silverstripe/silverstripe-omnipay@7dee9a1
  • 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

kinglozzer published the maintainer security advisory

Jun 6, 2022

Related news

CVE-2022-29858: Security Releases

Silverstripe silverstripe/assets through 1.10 allows XSS.

CVE-2022-29254: [CVE-2022-29254] Add extra validation on payment completion · silverstripe/silverstripe-omnipay@7dee9a1

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.