CVE-2024-57587

9.1 CRITICAL

📋 TL;DR

Multiple SQL injection vulnerabilities in EasyVirt DCScope and CO2Scope allow remote unauthenticated attackers to execute arbitrary SQL commands via login parameters. This affects all users running vulnerable versions of these products, potentially leading to complete system compromise.

💻 Affected Systems

Products:
  • EasyVirt DCScope
  • EasyVirt CO2Scope
Versions: DCScope <= 8.6.0, CO2Scope <= 1.3.0
Operating Systems: Any OS running these applications
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with default configurations are vulnerable

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full database compromise leading to data theft, privilege escalation, and complete system takeover via arbitrary SQL execution

🟠

Likely Case

Authentication bypass, data exfiltration, and potential remote code execution through database functions

🟢

If Mitigated

Limited impact with proper input validation and database permissions in place

🌐 Internet-Facing: HIGH - Unauthenticated remote exploitation via login endpoint
🏢 Internal Only: HIGH - Same vulnerability exists regardless of network exposure

🎯 Exploit Status

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

Exploitation requires no authentication and uses standard SQL injection techniques

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: DCScope > 8.6.0, CO2Scope > 1.3.0

Vendor Advisory: https://github.com/Elymaro/CVE/blob/main/EasyVirt/CVE-2024-57587.md

Restart Required: No

Instructions:

1. Check current version. 2. Update to latest version from vendor. 3. Verify patch applied. 4. Test login functionality.

🔧 Temporary Workarounds

Web Application Firewall

all

Deploy WAF with SQL injection rules to block malicious requests

Network Segmentation

all

Restrict access to vulnerable endpoints to trusted networks only

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries
  • Disable or restrict access to /api/auth/login endpoint

🔍 How to Verify

Check if Vulnerable:

Test login endpoint with SQL injection payloads in username/password fields

Check Version:

Check application version in admin interface or configuration files

Verify Fix Applied:

Attempt SQL injection after patch and verify it's blocked

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in logs
  • Unusual login attempts with special characters
  • Multiple failed login attempts from single IP

Network Indicators:

  • POST requests to /api/auth/login with SQL keywords
  • Unusual database connections from application server

SIEM Query:

source="application.logs" AND ("SQL" OR "syntax" OR "injection") AND uri="/api/auth/login"

🔗 References

📤 Share & Export