Bug 641224 (CVE-2010-3689)

Summary: CVE-2010-3689 OpenOffice.org: soffice insecure LD_LIBRARY_PATH setting
Product: [Other] Security Response Reporter: Huzaifa S. Sidhpurwala <huzaifas>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: caolanm, dtardon, jlieskov, jrusnack, security-response-team, vkrizan, wnefal+redhatbugzilla
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-29 13:09:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 642184, 642185, 642200, 642201, 804532    
Bug Blocks:    

Description Huzaifa S. Sidhpurwala 2010-10-08 04:58:24 UTC
Dmitri Gribenko discovered that the soffice script in the Openoffice.org package contained an insecure setting for the LD_LIBRARY_PATH, which could be abused by an attacker to execute arbitrary code.

The vulnerability is due to an insecure change to LD_LIBRARY_PATH, and
environment variable used by ld.so(8) to look for libraries in directories
other than the standard paths.  When there is an empty item in the
colon-separated list of directories in LD_LIBRARY_PATH, ld.so(8) treats it as a
'.' (current working directory).  If the given script is executed from a
directory where a local attacker could write files, there is a chance for

Currently in our soffice script we do...


while we should do...


so if someone currently does
then our LD_LIBRARY_PATH ends up as
which has an empty entry which effectively means


Red Hat would like to thank Dmitri Gribenko for reporting this issue.

Comment 4 Huzaifa S. Sidhpurwala 2011-01-27 03:52:06 UTC
Public via:

Comment 6 errata-xmlrpc 2011-01-28 13:02:39 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0182 https://rhn.redhat.com/errata/RHSA-2011-0182.html

Comment 7 errata-xmlrpc 2011-01-28 15:25:04 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0183 https://rhn.redhat.com/errata/RHSA-2011-0183.html