SQL Injection - Hypersonic SQL (Time Based)

The application appears vulnerable to time-based blind SQL injection in HyperSQL (HSQLDB) database contexts. This detector identifies vulnerabilities by injecting database-specific time delay functions and measuring response times to confirm SQL injection without relying on visible error messages or data output.

Time-based blind SQL injection allows attackers to extract sensitive data from the database by encoding information in response delays, even when the application does not display query results or errors. Attackers can systematically retrieve usernames, passwords, credit card numbers, and other confidential data character by character. Beyond data theft, attackers can modify database contents, execute stored procedures, read local files, and potentially achieve operating system command execution.

Do not trust client side input, even if there is client side validation in place. In general, type check all data on the server side. If the application uses JDBC, use PreparedStatement or CallableStatement, with parameters passed by '?' If the application uses ASP, use ADO Command Objects with strong type checking and parameterized queries. If database Stored Procedures can be used, use them. Do not concatenate strings into queries in the stored procedure, or use 'exec', 'exec immediate', or equivalent functionality! Do not create dynamic SQL queries using simple string concatenation. Escape all data received from the client. Apply an 'allow list' of allowed characters, or a 'deny list' of disallowed characters in user input. Apply the principle of least privilege by using the least privileged database user possible. In particular, avoid using the 'sa' or 'db-owner' database users. This does not eliminate SQL injection, but minimizes its impact. Grant the minimum database access that is necessary for the application.