CVE-2025-0793

6.3 MEDIUM

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks on ESAFENET CDG V5 systems via the flowId parameter in the /todoDetail.jsp file. Organizations using ESAFENET CDG V5 are affected, potentially exposing database contents and system control. The vulnerability is remotely exploitable and has public exploit details available.

💻 Affected Systems

Products:
  • ESAFENET CDG V5
Versions: Unknown specific versions, but all V5 versions appear vulnerable based on disclosure
Operating Systems: Unknown - likely Windows-based given typical CDG deployments
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the /todoDetail.jsp file and affects the flowId parameter. No specific configuration details are provided in the disclosure.

📦 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 allowing data extraction, modification, or deletion of sensitive information stored in the CDG application.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and network segmentation preventing exploitation attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily weaponizable. The vulnerability requires no authentication and has simple exploitation vectors.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Contact ESAFENET for security updates and monitor their security advisories.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block SQL injection patterns targeting the /todoDetail.jsp endpoint and flowId parameter

Input Validation Filter

all

Add server-side input validation to sanitize the flowId parameter before processing

🧯 If You Can't Patch

  • Network segmentation: Isolate CDG systems from internet access and restrict internal access to authorized users only
  • Database hardening: Implement least privilege database accounts, enable SQL injection protection features, and monitor for suspicious queries

🔍 How to Verify

Check if Vulnerable:

Test the /todoDetail.jsp endpoint with SQL injection payloads in the flowId parameter. Monitor for database errors or unexpected responses.

Check Version:

Check CDG application version through administrative interface or application metadata files

Verify Fix Applied:

Verify that SQL injection attempts against the flowId parameter are properly rejected or sanitized without affecting legitimate functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts following SQL injection patterns
  • HTTP requests to /todoDetail.jsp with suspicious flowId parameters

Network Indicators:

  • HTTP POST/GET requests containing SQL keywords (SELECT, UNION, etc.) in flowId parameter
  • Unusual traffic patterns to the CDG application

SIEM Query:

source="web_logs" AND url="/todoDetail.jsp" AND (flowId CONTAINS "SELECT" OR flowId CONTAINS "UNION" OR flowId CONTAINS "OR 1=1")

🔗 References

📤 Share & Export