Vulnerability from drupal
Published
2022-08-24 18:21
Modified
2023-08-10 19:26
Summary
Details

This module enables you to accept payments from the Elavon payment provider.

The module doesn't sufficiently verify that it's communicating with the correct server when using the Elavon (On-site) payment gateway, which could lead to leaking valid payment details as well as accepting invalid payment details.

This vulnerability is mitigated by the fact that an attacker must be able to spoof the Elavon DNS received by your site.

Credits

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003c2.3.0"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/commerce_elavon"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003c2.3.0"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/user/220112"
      ],
      "name": "Andy Fowlston"
    }
  ],
  "details": "This module enables you to accept payments from the Elavon payment provider.\n\nThe module doesn\u0027t sufficiently verify that it\u0027s communicating with the correct server when using the **Elavon (On-site)** payment gateway, which could lead to leaking valid payment details as well as accepting invalid payment details.\n\nThis vulnerability is mitigated by the fact that an attacker must be able to spoof the Elavon DNS received by your site.",
  "id": "DRUPAL-CONTRIB-2022-053",
  "modified": "2023-08-10T19:26:24.000Z",
  "published": "2022-08-24T18:21:02.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2022-053"
    }
  ],
  "schema_version": "1.7.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…