CVE-2025-11910

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 /MemoryState.do?Action=Query endpoint to execute arbitrary SQL commands. Organizations using this specific version of the Streamax Crocus system are affected.

💻 Affected Systems

Products:
  • Shenzhen Ruiming Technology Streamax Crocus
Versions: 1.3.40
Operating Systems: Unknown - likely various as it's a web application
Default Config Vulnerable: ⚠️ Yes
Notes: Only version 1.3.40 is confirmed affected; 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 OS command execution.

🟠

Likely Case

Unauthorized data access and extraction from the database, potentially including sensitive system information or user data.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and public exploit details exist.
🏢 Internal Only: MEDIUM - Still significant risk if internal attackers exist, but reduced exposure compared to internet-facing 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 with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available - 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

Input Validation and Sanitization

all

Implement server-side validation and sanitization of the orderField parameter to prevent SQL injection.

Implement parameterized queries or prepared statements in the application code

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

Configure WAF to block SQL injection patterns in the orderField parameter

🧯 If You Can't Patch

  • Block external access to the vulnerable endpoint using network controls or reverse proxy rules
  • Implement strict database permissions to limit potential damage from SQL injection

🔍 How to Verify

Check if Vulnerable:

Test the /MemoryState.do?Action=Query endpoint with SQL injection payloads in the orderField parameter and observe database errors or unexpected behavior.

Check Version:

Check the application version through administrative interface or configuration files; specific command depends on deployment.

Verify Fix Applied:

Test with the same SQL injection payloads after implementing fixes; successful fixes should return proper error messages or reject malicious input.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in orderField parameter values
  • Database error messages in application logs
  • Multiple failed login attempts or unusual query patterns

Network Indicators:

  • HTTP requests to /MemoryState.do?Action=Query with SQL keywords in parameters
  • Unusual database connection patterns from application server

SIEM Query:

source="web_logs" AND uri="/MemoryState.do" AND (param="orderField" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "--" OR value CONTAINS "' OR '1'='1")

🔗 References

📤 Share & Export