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

The vulnerability resides in the doFilter function of the findDeptPage.do file, where insufficient input sanitization of the sort argument enables SQL injection. The application fails to properly enforce authentication due to a path traversal bypass in the security filter, rendering all backend functions, including this injection point, accessible to unauthenticated remote attackers.

Successful exploitation allows an attacker to manipulate database queries, potentially leading to unauthorized data exfiltration, modification, or deletion of sensitive enterprise information. Given the nature of a Data Leakage Prevention system, the compromise of this platform could result in the total exposure of protected intellectual property and corporate secrets. With a CVSS score of 7.3, this flaw represents a significant risk to organizational confidentiality and integrity.

Immediate Action: As no vendor patch is currently available, restrict network access to the affected web interface to trusted management subnets only. If possible, disable the vulnerable findDeptPage.do functionality until the manufacturer provides an official security update.

Proactive Monitoring: Review web server and application access logs for suspicious patterns, particularly requests containing SQL syntax (e.g., SELECT, UNION, or delay-inducing functions) directed at the findDeptPage.do endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to inspect and block incoming requests containing malicious SQL payloads or attempting to bypass authentication through directory traversal patterns (e.g., /..;/).

Public Exploit Available: Yes — a published proof-of-concept exists as documented in the researcher's technical write-up on GitHub.

Given the availability of public proof-of-concept code and the critical nature of the affected system, immediate defensive action is required. Organizations must prioritize restricting network access to the vulnerable interface and implementing WAF-based filtering to mitigate the risk of exploitation while awaiting a formal patch from the vendor.