Bug 638371 (CVE-2010-3350) - CVE-2010-3350 bareftp: insecure library loading vulnerability
Summary: CVE-2010-3350 bareftp: insecure library loading vulnerability
Alias: CVE-2010-3350
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 638373
TreeView+ depends on / blocked
Reported: 2010-09-28 21:24 UTC by Vincent Danen
Modified: 2019-09-29 12:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-09 08:29:56 UTC

Attachments (Terms of Use)

Description Vincent Danen 2010-09-28 21:24:34 UTC
Raphael Geissert conducted a review of various packages in Debian and found that bareftp contained a script that could be abused by an attacker to execute arbitrary code [1].

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, /usr/bin/bareftp re-sets LD_LIBRARY_PATH insecurely:

export LD_LIBRARY_PATH=/usr/lib/bareftp:$LD_LIBRARY_PATH

A solution is to patch the script to test if $LD_LIBRARY_PATH is set first before attempting to modify it:

if [ -z ${LD_LIBRARY_PATH} ]; then
    export LD_LIBRARY_PATH=/usr/lib/foo
    export LD_LIBRARY_PATH=/usr/lib/foo:${LD_LIBRARY_PATH}

This issue has been assigned the name CVE-2010-3350.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598284

Comment 1 Vincent Danen 2010-09-28 21:25:49 UTC
Created bareftp tracking bugs for this issue

Affects: fedora-all [bug 638373]

Comment 2 Tomas Hoger 2010-09-29 07:42:57 UTC
This one-liner should work as an alternative to if-else-fi fix:

Note You need to log in before you can comment on or make changes to this bug.