Spring Boot's random value property source uses a weak PRNG unsuitable for secrets
Spring Boot
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot-cassandra Maven |
|
|
Spring Boot
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot-cassandra Maven |
|
|
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
From the CVE record · vmware
Spring Boot’s random value property source produces `${random.value}` values that are not suitable for secrets. An attacker may be able to exploit a secret generated this way; the input does not specify access or user-interaction requirements. `${random.uuid}` is not affected.
Check applications running Spring Boot 4.0.0–4.0.5, 3.5.0–3.5.13, 3.4.0–3.4.15, 3.3.0–3.3.18, or 2.7.0–2.7.32, as well as affected unsupported versions, particularly those using `spring-boot-cassandra`.