Spring Boot's PID file write follows symlinks at predictable default path
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 |
|
|
When an application is configured to use `ApplicationPidFileWriter`, a local attacker with write access to the PID file's location can corrupt one file on the host each time the application is started.
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); PID file / symlink behavior (`ApplicationPidFileWriter`). Versions that are no longer supported are also affected per vendor advisory.
From the CVE record · vmware
Spring Boot applications configured to use ApplicationPidFileWriter are vulnerable to PID file symlink behavior. A local attacker with write access to the PID file's location can corrupt one file on the host each time the application starts.
Check Spring Boot applications using ApplicationPidFileWriter on 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 reports that unsupported versions are affected.