Spring Data KeyValue - SpEL Injection vulnerability in SpelPropertyComparator
Spring Data KeyValue · Spring Data Redis
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-keyvalue Maven |
|
|
Spring Data KeyValue · Spring Data Redis
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-keyvalue Maven |
|
|
A SpEL Injection vulnerability exists in the Spring Data KeyValue if unsanitized user input is passed as Sort into a repository query method that delegates evaluation to the SpelPropertyComparator.
Affected versions: Spring Data KeyValue / Spring Data Redis 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.7.0 through 2.7.19.
From the CVE record · vmware
Spring Data KeyValue and Spring Data Redis are affected by SpEL injection when an application passes unsanitized user input as Sort to a repository query method that delegates evaluation to SpelPropertyComparator. An attacker who can supply that Sort input can inject a SpEL expression; the input does not specify whether authentication or other user interaction is required.
Engineers running Spring Data KeyValue or Spring Data Redis 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, or 2.7.0–2.7.19 should check their applications.