GitHub Advisoryadvisory · Packagist

GHSA-48f2-m7jg-866x Failed payment recorded has completed in Silverstripe Omnipay

LOW Published 2022-06-06 Modified 2022-06-06 Official page ↗
Aliases
CVE-2022-29254
Ecosystem
Packagist
Packages
silverstripe/silverstripe-omnipay
Severity
Low
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weaknesses
CWE-436, CWE-437
Reviewed
2022-06-06

Affected packages

• Packagist silverstripe/silverstripe-omnipay: < 2.5.2 → fixed in 2.5.2 • Packagist silverstripe/silverstripe-omnipay: >= 3.0.0, < 3.0.2 → fixed in 3.0.2 • Packagist silverstripe/silverstripe-omnipay: >= 3.1.0, < 3.1.4 → fixed in 3.1.4 • Packagist silverstripe/silverstripe-omnipay: >= 3.2.0, < 3.2.1 → fixed in 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: • Email us at [email protected]

Related

Alias · CVE (1)

  • CVE-2022-29254 silverstripe-omnipay is a SilverStripe integration with Omnipay PHP payments library. vulnerability

Weakness · CWE (2)

  • CWE-436 Interpretation Conflict weakness
  • CWE-437 Incomplete Model of Endpoint Features weakness

References