Skip to content

GHSA-c7j7-p5jq-26ff CVE-2014-1831

Insecure use of temporary files in passenger

Low RubyGems
Severity
Low
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
0.37%
Chance of exploitation in the next 30 days. Higher than 31.01% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
4.0.38
Upgrade passenger to this version or later

Description

Phusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on

  1. control_process.pid or
  2. a generation-* file.

Affected versions

RubyGems

PackageVulnerableFixed in
passenger
< 4.0.38
4.0.38

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 → 4.0.38

bundler
bundle update passenger # Gemfile: gem "passenger", ">= 4.0.38"

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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-whfx-877c-5p28
Insecure Permissions in Phusion Passenger
High 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
Is this in your code?

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