Skip to content
Fencer Intel
low 2.1

CVE-2014-1831 json

Insecure use of temporary files in passenger

published 11y ago modified 4mo ago also GHSA-c7j7-p5jq-26ff , EUVD-2018-0570

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Phusion Passenger before 4.0.37 allows local users to write to certain files and directories via a symlink attack on (1) control_process.pid or a (2) generation-* file.

Patch / fix

  • rubygems passenger 4.0.38
  • passenger Debian 14, Debian 13, Debian 12 4.0.37-1

debian advisories DEBIAN-CVE-2014-1831

Is CVE-2014-1831 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-1831 updated cvss 2.1

rubygem-passenger: insecure use of temporary files

  • Red Hat OpenStack Platform 4 rubygem-passenger, ruby193-rubygem-passenger
    affected: no fix planned “Will not fix”
  • Red Hat Software Collections ruby193-mod_passenger40, ruby193-rubygem-passenger40, ruby193-rubygem-passenger40-native, ruby193-rubygem-passenger40-native-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
rubygems passenger
<4.0.38
4.0.38

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.