A critical SQL injection vulnerability in the Tipray Data Leakage Prevention System version 1.0 allows unauthenticated remote attackers to compromise backend database integrity.

The application fails to sanitize the sort argument within the findRolePage function of the findSingConfigPage.do interface. This results in a SQL injection vulnerability that can be exploited by an unauthenticated attacker to manipulate backend database queries.

Successful exploitation of this vulnerability could lead to unauthorized data access, modification, or deletion within the database supporting the DLP system. Given the CVSS score of 7.3, this flaw poses a high risk to organizational confidentiality and integrity. If the database contains sensitive information or user credentials, the impact could extend to broader network compromise or the bypass of critical security controls.

Immediate Action: As there is no official patch available from the vendor, administrators should restrict network access to the affected interface to authorized IP addresses only.

Proactive Monitoring: Review web server and application access logs for suspicious POST requests to the findSingConfigPage.do endpoint containing SQL syntax or time-delay functions like SLEEP.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to inspect and block requests targeting the sort parameter that contain SQL injection patterns.

Public Exploit Available: Yes, a functional proof-of-concept is documented in a published research write-up on GitHub.

Due to the lack of a vendor-provided patch and the public availability of exploit details, this vulnerability presents a significant risk. Organizations utilizing Tipray Data Leakage Prevention System version 1.0 must immediately isolate the affected system from public-facing network segments and implement robust WAF filtering to prevent exploitation attempts until a permanent vendor fix is released.