CVE-2024-33972

9.8 CRITICAL

📋 TL;DR

A critical SQL injection vulnerability in Janobe products' payment module allows attackers to execute arbitrary SQL queries through the '/report/event_print.php' endpoint. This affects systems running version 1.0 of the PayPal, Credit Card and Debit Card Payment module. Attackers can potentially access and exfiltrate all database contents including sensitive payment information.

💻 Affected Systems

Products:
  • Janobe products with PayPal, Credit Card and Debit Card Payment module
Versions: 1.0
Operating Systems: Any OS running affected Janobe products
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the payment module specifically; requires the '/report/event_print.php' endpoint to be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to theft of all stored payment data, personal information, and potential lateral movement to other systems.

🟠

Likely Case

Data exfiltration of payment records, customer information, and potential credential harvesting from database tables.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing successful exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

SQL injection via URL parameter requires minimal technical skill; exploitation is straightforward once the vulnerable endpoint is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for patched version

Vendor Advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-janobe-products

Restart Required: Yes

Instructions:

1. Review vendor advisory for patched version. 2. Backup current installation. 3. Apply vendor-provided patch or update to fixed version. 4. Restart affected services. 5. Verify fix implementation.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block SQL injection patterns targeting the vulnerable endpoint

Endpoint Restriction

linux

Block external access to '/report/event_print.php' if not required for business operations

# Apache: RewriteRule ^/report/event_print\.php$ - [F]
# Nginx: location ~ ^/report/event_print\.php$ { return 403; }

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the application code
  • Deploy network segmentation to isolate affected systems and limit database access

🔍 How to Verify

Check if Vulnerable:

Test the '/report/event_print.php' endpoint with SQL injection payloads in the 'events' parameter and monitor for database errors or unexpected responses

Check Version:

Check application configuration or vendor documentation for module version information

Verify Fix Applied:

Attempt SQL injection tests after patching; successful attacks should be blocked and proper error handling should be observed

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in URL parameters
  • Multiple rapid requests to '/report/event_print.php'
  • Database error messages in application logs

Network Indicators:

  • SQL keywords in HTTP GET parameters
  • Unusual data volume from application server
  • Requests to database from unexpected sources

SIEM Query:

source="web_logs" AND url="/report/event_print.php" AND (param="events" CONTAINS "UNION" OR param="events" CONTAINS "SELECT" OR param="events" CONTAINS "' OR '")

🔗 References

📤 Share & Export