During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in turn can result in information disclosure and privilege escalation.
Weakness
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Passenger | Phusion | 5.3.0 (including) | 5.3.2 (excluding) |
| Passenger | Ubuntu | artful | * |
| Passenger | Ubuntu | cosmic | * |
| Passenger | Ubuntu | disco | * |
| Passenger | Ubuntu | eoan | * |
| Passenger | Ubuntu | groovy | * |
| Passenger | Ubuntu | hirsute | * |
| Passenger | Ubuntu | upstream | * |
| Ruby-passenger | Ubuntu | trusty | * |
Potential Mitigations
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/132.html
- https://cwe.mitre.org/data/definitions/17.html
- https://cwe.mitre.org/data/definitions/35.html
- https://cwe.mitre.org/data/definitions/76.html