CVE-2025-11912

6.3 MEDIUM

📋 TL;DR

This CVE describes a SQL injection vulnerability in Shenzhen Ruiming Technology's Streamax Crocus system version 1.3.40. Attackers can remotely exploit the 'orderField' parameter in the /DeviceState.do?Action=Query endpoint to execute arbitrary SQL commands. Organizations using this specific version of the Crocus system are affected.

💻 Affected Systems

Products:
  • Shenzhen Ruiming Technology Streamax Crocus
Versions: 1.3.40
Operating Systems: Not specified, likely embedded/Linux-based
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the specific version mentioned; other versions may also be vulnerable but not confirmed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full database compromise allowing data theft, modification, or deletion; potential system takeover through SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized data access, extraction of sensitive information from the database, and potential system disruption.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or minimal data exposure.

🌐 Internet-Facing: HIGH - The vulnerability can be exploited remotely, and the exploit has been published.
🏢 Internal Only: MEDIUM - Still significant risk from internal threats or compromised internal systems.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making exploitation straightforward for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: None - vendor did not respond to disclosure

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available, or implement workarounds.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF to filter malicious SQL injection attempts targeting the /DeviceState.do endpoint.

Input Validation Filter

all

Implement server-side validation to sanitize the 'orderField' parameter, allowing only expected values.

🧯 If You Can't Patch

  • Isolate the affected system from the internet and restrict network access to trusted IPs only.
  • Monitor database logs for unusual SQL queries and implement strict database user permissions.

🔍 How to Verify

Check if Vulnerable:

Test the /DeviceState.do?Action=Query endpoint with SQL injection payloads in the orderField parameter (e.g., orderField=1' OR '1'='1).

Check Version:

Check system version via web interface or configuration files; specific command depends on deployment.

Verify Fix Applied:

Retest with SQL injection payloads; successful fix should return error messages or no data instead of executing SQL.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • HTTP requests to /DeviceState.do with suspicious orderField values

Network Indicators:

  • HTTP traffic to /DeviceState.do containing SQL keywords (e.g., UNION, SELECT, DROP)

SIEM Query:

source="web_logs" AND uri="/DeviceState.do" AND (query="*orderField*" AND query="*' OR*" OR query="*UNION*" OR query="*SELECT*" OR query="*DROP*")

🔗 References

📤 Share & Export