CVE-2024-10134

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in ESAFENET CDG 5 allows remote attackers to execute arbitrary SQL commands via the 'servername' parameter in the connectLogout function. Organizations using ESAFENET CDG 5 are affected, potentially exposing database contents and system control.

💻 Affected Systems

Products:
  • ESAFENET CDG
Versions: Version 5
Operating Systems: All platforms running ESAFENET CDG 5
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of ESAFENET CDG 5 are vulnerable by default. No special configuration is required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, privilege escalation, and potential remote code execution on the underlying server.

🟠

Likely Case

Unauthorized database access, data exfiltration, and potential authentication bypass affecting system integrity.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and network segmentation in place.

🌐 Internet-Facing: HIGH - The vulnerability can be exploited remotely without authentication, making internet-facing instances particularly vulnerable.
🏢 Internal Only: HIGH - Even internal systems are vulnerable to exploitation from within the network perimeter.

🎯 Exploit Status

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

Exploit details have been publicly disclosed, making weaponization likely. The SQL injection is straightforward to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available - vendor did not respond to disclosure

Restart Required: No

Instructions:

No official patch available. Consider workarounds or alternative solutions.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block SQL injection patterns targeting the /com/esafenet/servlet/ajax/MultiServerAjax.java endpoint

Network Segmentation

all

Restrict access to ESAFENET CDG 5 instances to only trusted networks and IP addresses

🧯 If You Can't Patch

  • Isolate affected systems from internet access and restrict internal network access
  • Implement database-level protections including least privilege access and query logging

🔍 How to Verify

Check if Vulnerable:

Check if ESAFENET CDG 5 is installed and accessible. Attempt to access /com/esafenet/servlet/ajax/MultiServerAjax.java with SQL injection payloads in servername parameter.

Check Version:

Check application documentation or interface for version information. Typically found in admin panels or about pages.

Verify Fix Applied:

Test the vulnerable endpoint with SQL injection payloads to confirm they are properly sanitized or blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts or unusual parameter values in application logs
  • Requests to /com/esafenet/servlet/ajax/MultiServerAjax.java with suspicious servername parameters

Network Indicators:

  • Unusual outbound database connections from application server
  • SQL error messages in HTTP responses

SIEM Query:

source="application_logs" AND uri="/com/esafenet/servlet/ajax/MultiServerAjax.java" AND (param="servername" AND value MATCH "[';]|UNION|SELECT|INSERT|UPDATE|DELETE|DROP|CREATE")

🔗 References

📤 Share & Export