CVE-2025-34038

7.5 HIGH

📋 TL;DR

This SQL injection vulnerability in Weaver e-cology 8.0 allows unauthenticated attackers to execute arbitrary SQL queries through the getdata.jsp endpoint. Attackers can potentially extract sensitive data including administrator password hashes. All organizations running vulnerable versions of Weaver e-cology are affected.

💻 Affected Systems

Products:
  • Weaver e-cology
Versions: 8.0
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default configuration and requires no special setup to exploit.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including credential theft, data exfiltration, and potential lateral movement to other systems.

🟠

Likely Case

Extraction of administrator credentials leading to system takeover and data theft.

🟢

If Mitigated

Limited data exposure if proper input validation and WAF rules are in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Shadowserver Foundation observed exploitation in the wild on 2025-02-05 UTC.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Weaver official advisory

Vendor Advisory: https://weaver.com.co/products/ecology/

Restart Required: Yes

Instructions:

1. Contact Weaver support for the latest security patch. 2. Apply the patch following vendor instructions. 3. Restart the e-cology application server. 4. Verify the fix is applied.

🔧 Temporary Workarounds

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns targeting getdata.jsp

WAF-specific configuration commands vary by vendor

Endpoint Restriction

linux

Block external access to /weaver/weaver.file.getdata.jsp endpoint

iptables -A INPUT -p tcp --dport 80 -m string --string "getdata.jsp" --algo bm -j DROP
iptables -A INPUT -p tcp --dport 443 -m string --string "getdata.jsp" --algo bm -j DROP

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the application code
  • Deploy network segmentation to isolate the vulnerable system from sensitive data

🔍 How to Verify

Check if Vulnerable:

Test for SQL injection by sending crafted requests to /weaver/weaver.file.getdata.jsp?cmd=getSelectAllId&sql=test'

Check Version:

Check application version in admin panel or via /weaver/version.jsp

Verify Fix Applied:

Attempt SQL injection after patch application; successful queries should return error or no data

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple requests to getdata.jsp with SQL-like parameters
  • Failed login attempts following SQL injection patterns

Network Indicators:

  • HTTP requests containing SQL keywords (UNION, SELECT, etc.) targeting getdata.jsp
  • Unusual outbound database connections from application server

SIEM Query:

source="web_logs" AND uri="*getdata.jsp*" AND (query="*sql=*" OR query="*UNION*" OR query="*SELECT*" OR query="*--*" OR query="*'*" OR query="*%27*")

🔗 References

📤 Share & Export