Vulnerabilities (CVE)

Filtered by vendor Phusion Subscribe
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2012-6135 2 Phusion, Redhat 2 Passenger, Openshift 2019-11-21 6.4 MEDIUM 7.5 HIGH
RubyGems passenger 4.0.0 betas 1 and 2 allows remote attackers to delete arbitrary files during the startup process.
CVE-2018-12027 1 Phusion 1 Passenger 2019-10-03 6.5 MEDIUM 8.8 HIGH
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.
CVE-2018-12028 1 Phusion 1 Passenger 2019-10-03 6.8 MEDIUM 7.8 HIGH
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an error, it would cause Passenger's process manager to kill said reported arbitrary PID.
CVE-2018-12029 2 Debian, Phusion 2 Debian Linux, Passenger 2019-03-08 4.4 MEDIUM 7.0 HIGH
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but before it was chowned, leads to the target of the link being chowned via the path. Targeting sensitive files such as root's crontab file allows privilege escalation.
CVE-2016-10345 1 Phusion 1 Passenger 2017-04-24 4.6 MEDIUM 7.8 HIGH
In Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution, which could allow local attackers to gain the privileges of the passenger user.