Bug 747249

Summary:	Dereference of uninitialized value (ksh)
Product:	Red Hat Enterprise Linux 5	Reporter:	Pavel Raiskup <praiskup>
Component:	ksh	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	low	Docs Contact:
Priority:	low
Version:	5.8	CC:	kdudka, mfranc, ovasik, prc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ksh-20100621-4.el5	Doc Type:	Bug Fix
Doc Text:	No description necessary	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-21 05:51:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pavel Raiskup 2011-10-19 09:06:11 UTC

Dereference of uninitialized variable on src/lib/libdll/dllplug.c:82

There is string `dle->path` passed into dllcheck() function where this string is
used only for error output. Actually it looks it does not make sense to put
`dle->path` into dllcheck here -- probably there should be used `name` instead.
Anyway, variable `dle` may be uninitialized, so..

Program may crash here if the dllsopen() (on line 47) failed.

Version: ksh-20100621

This problem was newly found in RHEL 5.8 by coverity difference scan on RHEL packages 5.7 → 5.8.

Comment 1 Michal Hlavinka 2011-10-19 09:36:19 UTC

this is known issue, result of rebase. 

https://mailman.research.att.com/pipermail/ast-developers/2010q3/000729.html

We do not ship separate ksh (ast,...) libraries nor devel files, so this should not affect ksh in rhel5.

Comment 5 Michal Hlavinka 2012-01-23 14:42:15 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No description necessary

Comment 6 errata-xmlrpc 2012-02-21 05:51:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0159.html