CVE-2025-11912: SQL Injection in Shenzhen Ruiming Technology Streamax Crocus
A flaw has been found in Shenzhen Ruiming Technology Streamax Crocus 1.3.40. Affected is the function Query of the file /DeviceState.do?Action=Query. This manipulation of the argument orderField causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI Analysis
Technical Summary
CVE-2025-11912 is a SQL injection vulnerability affecting Shenzhen Ruiming Technology's Streamax Crocus software, specifically version 1.3.40. The vulnerability resides in the Query function accessed via the /DeviceState.do?Action=Query endpoint. The issue arises from improper sanitization of the orderField parameter, which is used directly in SQL queries without adequate validation or parameterization. This allows an attacker to inject malicious SQL code remotely, potentially extracting sensitive information, modifying database contents, or disrupting service availability. The vulnerability requires no authentication or user interaction, increasing its risk profile. The vendor was informed early but has not provided a patch or mitigation guidance, and a proof-of-concept exploit has been published publicly. The CVSS 4.0 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. The lack of vendor response and public exploit availability heighten the urgency for affected organizations to implement compensating controls. Streamax Crocus is typically used in video surveillance and security management, making the vulnerability particularly concerning for organizations relying on these systems for operational security.
Potential Impact
For European organizations, this vulnerability poses risks of unauthorized access to surveillance data, manipulation of device states, and potential disruption of security monitoring operations. Confidentiality could be compromised if attackers extract sensitive video or device information. Integrity risks include unauthorized modification of device states or logs, potentially masking malicious activity. Availability could be affected if attackers exploit the vulnerability to cause denial of service or system instability. Organizations in critical infrastructure, public safety, transportation, and private security sectors using Streamax Crocus are particularly vulnerable. The absence of a vendor patch increases exposure, and the public exploit availability raises the likelihood of attacks. Data protection regulations such as GDPR may impose additional compliance risks if personal data is exposed or compromised. The medium severity score suggests moderate but non-trivial impact, emphasizing the need for timely mitigation.
Mitigation Recommendations
Until an official patch is released, European organizations should implement strict network segmentation and firewall rules to restrict access to the /DeviceState.do endpoint, allowing only trusted management hosts. Deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the orderField parameter. Conduct thorough input validation and sanitization on any proxy or intermediary systems if applicable. Monitor logs for unusual query patterns or repeated access attempts to the vulnerable endpoint. Consider disabling or limiting the use of the Query function if operationally feasible. Engage with Shenzhen Ruiming Technology for updates and request a security patch. Regularly update incident response plans to include detection and containment strategies for SQL injection attacks. Additionally, perform security assessments on other components of the Streamax Crocus system to identify potential related vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Belgium, Poland, Sweden, Austria
CVE-2025-11912: SQL Injection in Shenzhen Ruiming Technology Streamax Crocus
Description
A flaw has been found in Shenzhen Ruiming Technology Streamax Crocus 1.3.40. Affected is the function Query of the file /DeviceState.do?Action=Query. This manipulation of the argument orderField causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI-Powered Analysis
Technical Analysis
CVE-2025-11912 is a SQL injection vulnerability affecting Shenzhen Ruiming Technology's Streamax Crocus software, specifically version 1.3.40. The vulnerability resides in the Query function accessed via the /DeviceState.do?Action=Query endpoint. The issue arises from improper sanitization of the orderField parameter, which is used directly in SQL queries without adequate validation or parameterization. This allows an attacker to inject malicious SQL code remotely, potentially extracting sensitive information, modifying database contents, or disrupting service availability. The vulnerability requires no authentication or user interaction, increasing its risk profile. The vendor was informed early but has not provided a patch or mitigation guidance, and a proof-of-concept exploit has been published publicly. The CVSS 4.0 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. The lack of vendor response and public exploit availability heighten the urgency for affected organizations to implement compensating controls. Streamax Crocus is typically used in video surveillance and security management, making the vulnerability particularly concerning for organizations relying on these systems for operational security.
Potential Impact
For European organizations, this vulnerability poses risks of unauthorized access to surveillance data, manipulation of device states, and potential disruption of security monitoring operations. Confidentiality could be compromised if attackers extract sensitive video or device information. Integrity risks include unauthorized modification of device states or logs, potentially masking malicious activity. Availability could be affected if attackers exploit the vulnerability to cause denial of service or system instability. Organizations in critical infrastructure, public safety, transportation, and private security sectors using Streamax Crocus are particularly vulnerable. The absence of a vendor patch increases exposure, and the public exploit availability raises the likelihood of attacks. Data protection regulations such as GDPR may impose additional compliance risks if personal data is exposed or compromised. The medium severity score suggests moderate but non-trivial impact, emphasizing the need for timely mitigation.
Mitigation Recommendations
Until an official patch is released, European organizations should implement strict network segmentation and firewall rules to restrict access to the /DeviceState.do endpoint, allowing only trusted management hosts. Deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the orderField parameter. Conduct thorough input validation and sanitization on any proxy or intermediary systems if applicable. Monitor logs for unusual query patterns or repeated access attempts to the vulnerable endpoint. Consider disabling or limiting the use of the Query function if operationally feasible. Engage with Shenzhen Ruiming Technology for updates and request a security patch. Regularly update incident response plans to include detection and containment strategies for SQL injection attacks. Additionally, perform security assessments on other components of the Streamax Crocus system to identify potential related vulnerabilities.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-10-17T13:01:59.545Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 68f2a4339c34d0947f40c744
Added to database: 10/17/2025, 8:16:51 PM
Last enriched: 10/17/2025, 8:31:56 PM
Last updated: 10/20/2025, 2:25:15 PM
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-11679: CWE-125 Out-of-bounds Read in warmcat libwebsockets
MediumCVE-2025-11680: CWE-787 Out-of-bounds Write in warmcat libwebsockets
MediumCVE-2025-11678: CWE-121 Stack-based Buffer Overflow in warmcat libwebsocket
HighCVE-2025-11677: CWE-416 Use After Free in warmcat libwebsockets
MediumCVE-2025-61455: n/a
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.