GHSA-5368-6h4h-gr29
Spring Boot's PID file write follows symlinks at predictable default path
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.springframework.boot:spring-boot-cassandra | >= 4.0.0, < 4.0.6 | 4.0.6 |
| Maven | org.springframework.boot:spring-boot-cassandra | >= 3.5.0, < 3.5.14 | 3.5.14 |
| Maven | org.springframework.boot:spring-boot-cassandra | >= 3.4.0, <= 3.4.15 | no fix listed |
| Maven | org.springframework.boot:spring-boot-cassandra | >= 3.3.0, <= 3.3.18 | no fix listed |
| Maven | org.springframework.boot:spring-boot-cassandra | <= 2.7.32 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.