Spring Data Relational Parameter not Escaped for Query By Example LIKE Pattern
Spring Data Relational · Spring Data JDBC · Spring Data R2DBC
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-relational Maven |
|
|
Spring Data Relational · Spring Data JDBC · Spring Data R2DBC
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-relational Maven |
|
|
Spring Data Relational does not properly escape binding values of externally-controlled input when using StringMatcher (STARTING, ENDING, or CONTAINING) in Query By Example (QBE). An attacker can supply wildcard characters to perform boolean-based blind data inference.
Affected versions: Spring Data Relational/JDBC/R2DBC 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.4.0 through 2.4.19.
From the CVE record · vmware
Spring Data Relational does not properly escape externally controlled binding values when Query By Example uses the STARTING, ENDING, or CONTAINING StringMatcher. An attacker who can supply wildcard characters to such a query can perform boolean-based blind data inference. The input does not specify whether authentication or user interaction is required.
Teams running Spring Data Relational, JDBC, or R2DBC should check versions 4.0.0–4.0.5, 3.5.0–3.5.11, 3.4.0–3.4.14, 3.3.0–3.3.16, 3.2.0–3.2.15, 3.1.0–3.1.14, 3.0.0–3.0.15, and 2.4.0–2.4.19.