CriticalGHSA-7cv3-gvmc-8mq5CVE-2018-12026

Phusion Passenger SpawningKit Contains Arbitrary Read/Write Vulnerability

Published 14 May 2022 · Updated 20 Feb 2024

Is your project on an affected passenger?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

passengerRubyGems
Affected
>=5.3.0 <5.3.2
Fixed in
5.3.2
Update to the fixed version for your release line, for example:bundle update --conservative passenger # Gemfile: '>= 5.3.2'

Details

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.

Is GHSA-7cv3-gvmc-8mq5 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
  • 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
  • HighCVE-2018-12027Insecure Permissions in Phusion Passenger · 13 May 2022
  • MediumCVE-2017-16355Phusion Passenger information disclosure · 13 May 2022
All 14 advisories for passenger

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.