Gentoo Logo

Ruby: CGI::Session creates files insecurely

Content:

1.  Gentoo Linux Security Advisory

Version Information

Advisory Reference GLSA 200409-08 / dev-lang/ruby
Release Date September 03, 2004
Latest Revision September 03, 2004: 01
Impact normal
Exploitable local
Package Vulnerable versions Unaffected versions Architecture(s)
dev-lang/ruby < 1.8.2_pre2 revision >= 1.6.8-r11, revision >= 1.8.0-r7, >= 1.8.2_pre2 All supported architectures

Related bugreports: #60525

Synopsis

When used for CGI scripting, Ruby creates session files in /tmp with the permissions of the default umask. Depending on that umask, local users may be able to read sensitive data stored in session files.

2.  Impact Information

Background

Ruby is an Object Oriented, interpreted scripting language used for many system scripting tasks. It can also be used for CGI web applications.

Description

The CGI::Session::FileStore implementation (and presumably CGI::Session::PStore), which allow data associated with a particular Session instance to be written to a file, writes to a file in /tmp with no regard for secure permissions. As a result, the file is left with whatever the default umask permissions are, which commonly would allow other local users to read the data from that session file.

Impact

Depending on the default umask, any data stored using these methods could be read by other users on the system.

3.  Resolution Information

Workaround

By changing the default umask on the system to not permit read access to other users (e.g. 0700), one can prevent these files from being readable by other users.

Resolution

All Ruby users should upgrade to the latest version:

Code Listing 3.1: Resolution

# emerge sync
# emerge -pv ">=dev-lang/ruby-your_version"
# emerge ">=dev-lang/ruby-your_version"

4.  References



Print

Page updated September 03, 2004

Summary: This is a Gentoo Linux Security Advisory

Security Team
Contact Address

Donate to support our development efforts.

Copyright 2001-2014 Gentoo Foundation, Inc. Questions, Comments? Contact us.