Spring Boot accepts predictable temp directory without ownership verification
Spring Boot
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot Maven |
|
|
Spring Boot
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.boot:spring-boot Maven |
|
|
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.
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); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
From the CVE record · vmware
Spring Boot’s ApplicationTemp directory may be taken over by a local attacker on the same host. If server.servlet.session.persistent is true and the attack persists across application restarts, the attacker may read session information and hijack authenticated users or execute code as the application’s user through a gadget chain.
Check Spring Boot applications running versions 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; the vendor also identifies unsupported versions as affected.