GHSA-whfx-877c-5p28 CVE-2018-12027
Insecure Permissions in Phusion Passenger
- Severity
- 8.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.07%
- Chance of exploitation in the next 30 days. Higher than 64.89% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
5.3.2- Upgrade passenger to this version or later
Description
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.
Affected versions
RubyGems
| Package | Vulnerable | Fixed in |
|---|---|---|
| passenger | >= 5.3.0, < 5.3.2 |
5.3.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
passenger RubyGems → 5.3.2
- bundler
bundle update passenger # Gemfile: gem "passenger", ">= 5.3.2"
Severity breakdown
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-2cj2-qqxj-5m3r Phusion Passenger denial of service | High | Also affects passenger |
| GHSA-jjcj-fgfm-9g9r Phusion Passenger Race Condition Allows Privilege Escalation | High | Also affects passenger |
| GHSA-7cv3-gvmc-8mq5 Phusion Passenger SpawningKit Contains Arbitrary Read/Write Vulnerability | Critical | Also affects passenger |
| GHSA-4284-jfhc-f854 Phusion Passenger incorrect permission assignment | Medium | Also affects passenger |
| GHSA-jjhj-8gx7-x836 Incorrect Access Control in Phusion Passenger | High | Also affects passenger |
| GHSA-cv3f-px9r-54hm Phusion Passenger information disclosure | Medium | Also affects passenger |
| GHSA-8mw8-j583-vqfg RubyGems passenger gem allows remote attackers to delete files | High | Also affects passenger |
| GHSA-qw8w-2xcp-xg59 Insecure use of temporary files in Phusion passenger | Low | Also affects passenger |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor