CWE-564 상세 정보

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

취약점 도입 방식

Architecture and Design
Implementation

적용 가능한 플랫폼

언어

이름: SQL (Often)

기술

이름: Database Server (Undetermined)

일반적인 결과

관찰된 예시

잠재적 완화 방법

Phases : Requirements
A non-SQL style database that is not subject to this flaw may be chosen.
Phases : 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.
Phases : 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.
Phases : Implementation
Implement SQL strings using prepared statements that bind variables. Prepared statements that do not bind variables can be vulnerable to attack.
Phases : 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.)
효과성 : High

취약점 매핑 메모

근거 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
댓글 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

관련 공격 패턴

메모

This weakness might be referred to as "SQL injection" because Hibernate processes HQL queries by translating them into SQL queries. However, HQL is a distinct language.

참고 자료

REF-1559

Hibernate
OWASP.
https://community.owasp.org/Hibernate

REF-1560

Hibernate Query Language (HQL) Injection
Invicti.
https://www.invicti.com/web-application-vulnerabilities/hibernate-query-language-hql-injection

REF-1534

Automated Technical Debt Measure, Version 2
OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF

제출

수정 사항