Values produced by ${random.value} are not suitable for use as secrets
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.7.33, 3.3.19, 3.4.16 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=2.7.0 <2.7.33, >=3.3.0 <3.3.19, >=3.4.0 <3.4.16, >=3.5.0 <3.5.14, >=4.0.0 <4.0.6 | 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket