Payment-Data-Leak - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/payment-data-leak/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 29 Jan 2024 12:00:00 +0000AVideo Unauthenticated Access to Payment Log DataTables Endpointshttps://feed.craftedsignal.io/briefs/2024-01-29-avideo-auth-bypass/Mon, 29 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-29-avideo-auth-bypass/AVideo is vulnerable to unauthenticated access to multiple `list.json.php` endpoints due to missing authorization checks, allowing attackers to retrieve sensitive payment transaction records, including PayPal billing agreement IDs, Express Checkout tokens, Authorize.Net webhook payloads, and Bitcoin payment records, leading to financial data exposure and potential PII leakage.AVideo, a video sharing platform, contains a critical vulnerability affecting multiple payment plugins. The vulnerability stems from the lack of authentication checks on list.json.php endpoints, which expose sensitive payment transaction data. This oversight allows unauthenticated attackers to retrieve payment records from PayPal, Authorize.Net, and Bitcoin payment providers. The issue mirrors a previously patched vulnerability in the Scheduler plugin (GHSA-j724-5c6c-68g5) but was not consistently applied across all affected endpoints. A total of 21 list.json.php endpoints remain vulnerable. The affected version is <= 26.0. This vulnerability poses a significant threat to AVideo users, potentially leading to financial data theft and unauthorized access to sensitive information.

Attack Chain

  1. An unauthenticated attacker identifies a vulnerable AVideo instance.
  2. The attacker crafts a GET request to a vulnerable list.json.php endpoint, such as plugin/PayPalYPT/View/PayPalYPT_log/list.json.php.
  3. The AVideo server processes the request without authentication and executes the associated PHP script.
  4. The script queries the database, retrieving all records from the corresponding table (e.g., PayPalYPT_log).
  5. The server returns a JSON-encoded response containing the retrieved data, including sensitive payment information.
  6. The attacker parses the JSON response to extract PayPal agreement IDs, Express Checkout tokens, Authorize.Net webhook payloads, or Bitcoin transaction details.
  7. The attacker uses the extracted tokens or payment information for malicious purposes, such as payment manipulation or account correlation.

Impact

Successful exploitation of this vulnerability leads to significant data exposure. Attackers can retrieve all payment transaction records across PayPal, Authorize.Net, and Bitcoin payment providers. This includes sensitive data such as PayPal Express Checkout tokens and billing agreement IDs, potentially enabling payment manipulation or account correlation. Transaction records contain user ID mappings, payment amounts, and full API responses that may include payer email addresses and names. The scope is broad, affecting 21 list.json.php endpoints, also exposing live streaming server infrastructure and user connection data. No authentication or user interaction is required.

Recommendation

  • Apply the provided code snippet to all unprotected list.json.php endpoints to enforce authentication checks using User::isAdmin() as detailed in the advisory's recommended fix.
  • Monitor web server access logs for requests to list.json.php endpoints located within AVideo plugin directories using the rule AVideo Unauthenticated Access to list.json.php.
  • Inspect network traffic for sensitive data being transmitted in cleartext from the vulnerable endpoints, such as PayPal tokens, using the rule AVideo Sensitive Data Exposure via Unauthenticated Endpoint.
]]>highadvisoryavideoauthentication-bypasspayment-data-leak