Bug 1161499 (CVE-2014-7818) - CVE-2014-7818 rubygem-actionpack: arbitrary file existence disclosure
Summary: CVE-2014-7818 rubygem-actionpack: arbitrary file existence disclosure
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2014-7818
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1163511
Blocks: 1159118
TreeView+ depends on / blocked
 
Reported: 2014-11-07 09:12 UTC by Ján Rusnačko
Modified: 2021-02-17 06:02 UTC (History)
48 users (show)

Fixed In Version: rubygem-actionpack 3.2.20, rubygem-actionpack 4.0.11, rubygem-actionpack 4.1.7, rubygem-actionpack 4.2.0.beta3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-12 21:48:15 UTC


Attachments (Terms of Use)

Description Ján Rusnačko 2014-11-07 09:12:00 UTC
The following Ruby on Rails issue was reported[1]:

""
Arbitrary file existence disclosure in Action Pack

There is an information leak vulnerability in Action Pack. This vulnerability
has been assigned the CVE identifier CVE-2014-7818.

Versions Affected:  >= 3.0.0
Not affected:       <= 3.0.0
Fixed Versions:     3.2.20, 4.0.11, 4.1.7, 4.2.0.beta3

Impact
------
Specially crafted requests can be used to determine whether a file exists on the filesystem that is outside the Rails application's root directory.  The files will not be served, but attackers can determine whether or not the file exists.

This only impacts Rails applications that enable static file serving at
runtime.  For example, the application's production configuration will say:

  config.serve_static_assets = true

All users running an affected release should either upgrade or use one of the work arounds immediately.

Releases
--------
The 3.2.20, 4.0.11, 4.1.7 & 4.2.0.beta3 releases are available at the normal locations.

Workarounds
-----------
To work around this issue, set config.serve_static_assets = false in an initializer.  This work around will not be possible in all hosting environments and upgrading is advised.

""

[1] https://groups.google.com/forum/#!topic/rubyonrails-security/dCp7duBiQgo

Comment 1 Ján Rusnačko 2014-11-07 09:27:44 UTC
External References:

https://groups.google.com/forum/#!topic/rubyonrails-security/dCp7duBiQgo

Comment 3 Ján Rusnačko 2014-11-07 10:05:08 UTC
Acknowledgements:

Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Eaden McKee, Dennis Hackethal & Christian Hansen of Crowdcurity, Juan C. Müller & Mike McClurg of Greenhouse.io, and Alex Ianus of Coinbase as the independent, original reporters.

Comment 4 Vincent Danen 2014-11-12 21:48:15 UTC
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Comment 5 Vincent Danen 2014-11-12 21:48:42 UTC
Created rubygem-actionpack tracking bugs for this issue:

Affects: fedora-all [bug 1163511]


Note You need to log in before you can comment on or make changes to this bug.