Spring Data REST Querydsl integration exposes Jackson-hidden persistent fields as filter keys
Spring Data REST
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-rest-core Maven |
|
|
Spring Data REST
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-rest-core Maven |
|
|
Spring Data REST's Querydsl integration accepts arbitrary persistent property paths as request-parameter filter keys and does not consider Jackson customizations before handing them to Querydsl.
Affected versions: Spring Data REST 3.7.0 through 3.7.19; 4.3.0 through 4.3.16; 4.4.0 through 4.4.14; 4.5.0 through 4.5.11; 5.0.0 through 5.0.5.
From the CVE record · vmware
Spring Data REST's Querydsl integration accepts arbitrary persistent property paths as request-parameter filter keys without considering Jackson customizations. An attacker can submit filter keys for those paths when Querydsl filtering is available; the input does not specify authentication or user-interaction requirements.
Engineers running Spring Data REST 3.7.0–3.7.19, 4.3.0–4.3.16, 4.4.0–4.4.14, 4.5.0–4.5.11, or 5.0.0–5.0.5 should check their applications.