CVE-2025-41013

9.8 CRITICAL

📋 TL;DR

This SQL injection vulnerability in TCMAN GIM v11 allows attackers to manipulate database queries through the 'idmant' parameter in GET requests to '/PC/frmEPIS.aspx'. Attackers can retrieve, modify, create, or delete database content. Organizations using TCMAN GIM v11 version 20250304 are affected.

💻 Affected Systems

Products:
  • TCMAN GIM
Versions: v11 version 20250304
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with the vulnerable version are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, and potential system takeover via subsequent attacks.

🟠

Likely Case

Unauthorized data access and modification leading to data integrity loss and potential business disruption.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage scope.

🌐 Internet-Facing: HIGH - The vulnerable endpoint is accessible via web requests, making internet-facing instances immediately vulnerable.
🏢 Internal Only: HIGH - Even internal systems are vulnerable to insider threats or compromised internal accounts.

🎯 Exploit Status

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

SQL injection via GET parameter requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-tcman-gim-2

Restart Required: No

Instructions:

1. Monitor vendor for patch release. 2. Apply patch when available. 3. Test in non-production environment first.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns targeting the vulnerable endpoint.

Input Validation Filter

all

Implement server-side validation to sanitize 'idmant' parameter before processing.

🧯 If You Can't Patch

  • Block external access to '/PC/frmEPIS.aspx' at network perimeter.
  • Implement strict database user permissions with least privilege principle.

🔍 How to Verify

Check if Vulnerable:

Test the endpoint with SQL injection payloads in the 'idmant' parameter and observe database errors or unexpected responses.

Check Version:

Check application version in admin interface or configuration files.

Verify Fix Applied:

Retest with SQL injection payloads after applying fixes; successful attacks should be blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple requests to '/PC/frmEPIS.aspx' with suspicious 'idmant' values

Network Indicators:

  • GET requests to '/PC/frmEPIS.aspx' containing SQL keywords in parameters

SIEM Query:

source="web_logs" AND uri="/PC/frmEPIS.aspx" AND (param="idmant" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "OR 1=1")

🔗 References

📤 Share & Export