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 exploitation. Currently in our soffice script we do... LD_LIBRARY_PATH=$my_path${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH} while we should do... LD_LIBRARY_PATH=$my_path${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} so if someone currently does export LD_LIBRARY_PATH= then our LD_LIBRARY_PATH ends up as LD_LIBRARY_PATH=/path: which has an empty entry which effectively means LD_LIBRARY_PATH=/path:. Acknowledgements: Red Hat would like to thank Dmitri Gribenko for reporting this issue.
Public via: http://www.openoffice.org/security/cves/CVE-2010-3689.html
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
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