Bug 950930 – CVE-2013-1945 ruby193: insecure LD_LIBRARY_PATH setting

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 950930 - (CVE-2013-1945) CVE-2013-1945 ruby193: insecure LD_LIBRARY_PATH setting

Summary:	CVE-2013-1945 ruby193: insecure LD_LIBRARY_PATH setting

Status:	CLOSED DEFERRED

Aliases:	CVE-2013-1945

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20140917,reported=2...
Keywords:	Security

Depends On:	949031
Blocks:	950932
	Show dependency tree / graph

Reported:	2013-04-11 04:31 EDT by Kurt Seifried
Modified:	2014-11-25 14:56 EST (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-09-17 20:07:09 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kurt Seifried 2013-04-11 04:31:05 EDT

Tomas Hoger (thoger@redhat.com) reports:

Description of problem:

$ grep LD_LIBRARY_PATH /opt/rh/ruby193/enable 
export LD_LIBRARY_PATH=/opt/rh/ruby193/root/usr/lib64:$LD_LIBRARY_PATH

$ touch libc.so.6

$ scl enable ruby193 bash
bash: error while loading shared libraries: libc.so.6: file too short

$ rpm -q ruby193-runtime 
ruby193-runtime-1-6.el6.x86_64

Comment 2 Kurt Seifried 2014-09-17 20:05:48 EDT

Statement:

This issue affects the versions of Ruby 193 as shipped with Red Hat OpenShift Enterprise 1. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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