Insecure Permissions in Phusion Passenger
Published 13 May 2022 · Updated 16 Feb 2024
Is your project on an affected passenger?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=5.3.0 <5.3.2
- Fixed in
- 5.3.2
bundle update --conservative passenger # Gemfile: '>= 5.3.2'Details
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said socket are writable by a normal user that is not the application's user, then that non-application user can swap that directory with something else, resulting in traffic being redirected to a non-application user's process through an alternative Unix domain socket.
Is GHSA-whfx-877c-5p28 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected passenger, and gives you the command that fixes it.
More advisories for passenger
- MediumCVE-2025-26803Phusion Passenger denial of service · 24 Feb 2025
- CriticalCVE-2018-12026Phusion Passenger SpawningKit Contains Arbitrary Read/Write Vulnerability · 14 May 2022
- HighCVE-2018-12029Phusion Passenger Race Condition Allows Privilege Escalation · 14 May 2022
- MediumCVE-2018-12615Phusion Passenger incorrect permission assignment · 13 May 2022
- HighCVE-2018-12028Incorrect Access Control in Phusion Passenger · 13 May 2022
- MediumCVE-2017-16355Phusion Passenger information disclosure · 13 May 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.