Bug 644606 (CVE-2010-4005)

Summary: CVE-2010-4005 tomboy: insecure library loading vulnerability
Product: [Other] Security Response Reporter: Vincent Danen <vdanen>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-10 10:57:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 644956    
Bug Blocks:    

Description Vincent Danen 2010-10-19 20:16:11 UTC
Ludwig Nussel discovered that tomboy contained a script that 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.

In Fedora, both /usr/bin/tomboy and /usr/bin/tomboy-panel re-set LD_LIBRARY_PATH insecurely:

export LD_LIBRARY_PATH="/usr/lib/tomboy${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"

A solution is to patch the script to use ':+:' properly:

export LD_LIBRARY_PATH=/usr/lib/foo${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}

Comment 1 Vincent Danen 2010-10-20 16:39:37 UTC
Created tomboy tracking bugs for this issue

Affects: fedora-all [bug 644956]

Comment 2 Product Security DevOps Team 2019-06-10 10:57:24 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.