How severe is CVE-2014-1831?

CVE-2014-1831 has a CVSS 2.0 base score of 2.1, rated low severity.

Is CVE-2014-1831 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2014-1831?

CVE-2014-1831 affects Phusion Passenger. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2014-1831?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2014-1831 published?

CVE-2014-1831 was published on 2015-02-19 and last updated on 2026-06-17.

CVE-2014-1831

CVE-2014-1831 is a low-severity vulnerability in Phusion Passenger with a CVSS 2.0 base score of 2.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 2.0 base score 2.1)
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phusion Passenger
Published: 2015-02-19
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2014-1831?: 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.
How severe is CVE-2014-1831?: CVE-2014-1831 has a CVSS 2.0 base score of 2.1, rated low severity.
Is CVE-2014-1831 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2014-1831?: CVE-2014-1831 affects Phusion Passenger. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2014-1831?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2014-1831 published?: CVE-2014-1831 was published on 2015-02-19 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:phusion:passenger:*:*:*:*:*:*:*:*

More vulnerabilities in Phusion Passenger

CVE-2018-12026 — Critical (CVSS 9.8): During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2…
CVE-2018-12027 — High (CVSS 8.8): An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information…
CVE-2018-12028 — High (CVSS 7.8): An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a…
CVE-2016-10345 — High (CVSS 7.8): In Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution,…
CVE-2012-6135 — High (CVSS 7.5): RubyGems passenger 4.0.0 betas 1 and 2 allows remote attackers to delete arbitrary files during the startup process.
CVE-2018-12029 — High (CVSS 7.0): A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of…

All CVEs affecting Phusion Passenger →