Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Packagist package

silverstripe/silverstripe-omnipay

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.7PackagistPublished

    Failed payment recorded has completed in Silverstripe Omnipay

    CVE-2022-29254 · GHSA-48f2-m7jg-866x

    Affected
    • Packagist silverstripe/silverstripe-omnipay < 2.5.2; >= 3.0.0, < 3.0.2; >= 3.1.0, < 3.1.4; >= 3.2.0, < 3.2.1
    Fixed in
    3.2.13.0.22.5.23.1.4· Vendor fix available
    Issue
    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 security@silverstripe.org

    Recommended action: Upgrade to 3.2.1, 3.1.4, 3.0.2 or 2.5.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →