glibc2 does not properly clear the LD_DEBUG_OUTPUT and LD_DEBUG environmental variables when a program is spawned from a setuid program, which could allow local users to overwrite files via a symlink attack.Referenceshttp://www.securityfocus.com/bid/1719https://exchange.xforce.ibmcloud.com/vulnerabilities/5299http://www.securityfocus.com/archive/1/85028
