Spring Data web support unbounded negative-result cache keyed on attacker-supplied property names
Spring Data Commons
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-commons Maven |
|
|
Spring Data Commons
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.data:spring-data-commons Maven |
|
|
Spring Data's internal property-lookup cache accepts and permanently retains attacker-supplied strings as cache keys, allowing heap exhaustion through repeated requests.
Affected versions: Spring Data Commons 2.7.0 through 2.7.19; 3.3.0 through 3.3.16; 3.4.0 through 3.4.14; 3.5.0 through 3.5.11; 4.0.0 through 4.0.5.
From the CVE record · vmware
Spring Data Commons permanently retains attacker-supplied strings as keys in its internal property-lookup cache. If an application passes attacker-controlled strings to property lookup, repeated requests can exhaust its heap. The input does not specify whether authentication or user interaction is required.
Engineers running Spring Data Commons 2.7.0–2.7.19, 3.3.0–3.3.16, 3.4.0–3.4.14, 3.5.0–3.5.11, or 4.0.0–4.0.5 should check their deployments.