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

@kinglozzer kinglozzer published to silverstripe/silverstripe-omnipay Jun 6, 2022
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

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.061%
(27th percentile)

Weaknesses

CVE ID

CVE-2022-29254

GHSA ID

GHSA-48f2-m7jg-866x

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.