CVE-2013-2119: Medium severity phusion passenger vulnerability

Published Jan 7, 2013
·
Updated

Michael Scherer reported that the passenger ruby gem, when used in standalone mode, does not use temporary files in a secure manner. In the lib/phusionpassenger/standalone/main.rb's createnginxcontroller function, passenger creates an nginx configuration file insecurely and starts nginx with that configuration file:

@tempdir = "/tmp/passenger-standalone.#{$$}" @configfilename = "#{@tempdir}/config"

If a local attacker were able to create a temporary directory that passenger uses and supply a custom nginx configuration file they could start an nginx instance with their own configuration file. This could result in a denial of service condition for a legitimate service or, if passenger were executed as root (in order to have nginx listen on port 80, for instance), this could lead to a local root compromise.

Other sources

Phusion Passenger gem before 3.0.21 and 4.0.x before 4.0.5 for Ruby allows local users to cause a denial of service (prevent application start) or gain privileges by pre-creating a temporary "config" file in a directory with a predictable name in /tmp/ before it is used by the gem.

MITRE

Affected Software

26 affected components
Phusion Passenger<=3.0.20
Phusion Passenger=3.0.0
Phusion Passenger=3.0.1
Phusion Passenger=3.0.2
Phusion Passenger=3.0.3
Phusion Passenger=3.0.4
Phusion Passenger=3.0.5
Phusion Passenger=3.0.6
Phusion Passenger=3.0.7
Phusion Passenger=3.0.8
Phusion Passenger=3.0.9
Phusion Passenger=3.0.10
Phusion Passenger=3.0.11
Phusion Passenger=3.0.12
Phusion Passenger=3.0.13
Phusion Passenger=3.0.14
Phusion Passenger=3.0.15
Phusion Passenger=3.0.17
Phusion Passenger=3.0.18
Phusion Passenger=3.0.19
Phusion Passenger=4.0.1
Phusion Passenger=4.0.2
Phusion Passenger=4.0.3
Phusion Passenger=4.0.4
ruby-lang Ruby
redhat Openshift=1.0

Event History

Jan 7, 2013
Data Sourced
10:05 PM
DescriptionSeverityAffected Software
Jan 2, 2014
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-2119?

CVE-2013-2119 has a moderate severity rating due to potential security risks associated with insecure file handling.

2

How do I fix CVE-2013-2119?

To mitigate CVE-2013-2119, you should upgrade to Phusion Passenger version 3.0.21 or higher.

3

Which versions of Phusion Passenger are affected by CVE-2013-2119?

CVE-2013-2119 affects Phusion Passenger versions up to and including 3.0.20 and certain 4.0.x versions.

4

What is the impact of CVE-2013-2119?

The impact of CVE-2013-2119 could lead to unauthorized access due to the insecure handling of temporary files.

5

Is CVE-2013-2119 related to any specific software?

CVE-2013-2119 specifically affects the Phusion Passenger Ruby gem when utilized in standalone mode.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203