An attacker on the same network as the remote application may be able to utilize a timing attack to discover information about the remote…
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.
An attacker on the same network as the remote application may be able to utilize a timing attack to discover information about the remote secret. In extreme circumstances this could result in the attacker determining the secret and uploading changed classes, thereby achieving remote code execution in the remote application. 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); DevTools remote secret comparison. 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