CWE-564 Use of Hibernate with HQL/SQL Query String Containing External Input

The product uses Hibernate to execute a dynamic HQL or SQL statement, but the statement is built with user-controlled input.

• Confidentiality, Integrity: Read Application Data, Modify Application Data — If an attacker can insert input directly into the SQL query string, even when the string contains parameter bindings, an attacker can modify the statement's structure and meaning, possibly execute arbitrary SQL commands (i.e., SQL injection).

• [Requirements] A non-SQL style database that is not subject to this flaw may be chosen. • [Architecture and Design] Follow the principle of least privilege when creating user accounts to a SQL database. Users should only have the minimum privileges necessary to use their account. If the requirements of the system indicate that a user can read and modify their own data, then limit their privileges so they cannot read/write others' data. • [Architecture and Design] For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server. • [Implementation] Implement SQL strings using prepared statements that bind variables. Prepared statements that do not bind variables can be vulnerable to attack. • [Implementation] Use vigorous allowlist style checking on any user input that may be used in a SQL command. Rather than escape meta-characters, it is safest to disallow them entirely. Reason: Later use of data that have been entered in the database may neglect to escape meta-characters before use. Narrowly define the set of safe characters based on the expected value of the parameter in the request.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

• CVE-2025-52472: wiki platform REST API allows HQL injection via select and order clauses. • CVE-2023-26093: middleware allows HQL injection via sort columns. • CVE-2016-1595: file download functionality in service desk software allows HQL injection via user-controlled parameters