Bug 1439693 - (CVE-2017-7418) CVE-2017-7418 proftpd: AllowChrootSymlinks control bypass
CVE-2017-7418 proftpd: AllowChrootSymlinks control bypass
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170306,repor...
: Security
Depends On: 1439696 1439695
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-06 08:09 EDT by Andrej Nemec
Modified: 2017-04-19 09:12 EDT (History)
4 users (show)

See Also:
Fixed In Version: proftpd 1.3.5e, proftpd 1.3.6rc5
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-04-06 08:09:57 EDT
ProFTPD before 1.3.5e and 1.3.6 before 1.3.6rc5 controls whether the home directory of a user could contain a symbolic link through the AllowChrootSymlinks configuration option, but checks only the last path component when enforcing AllowChrootSymlinks. Attackers with local access could bypass the AllowChrootSymlinks control by replacing a path component (other than the last one) with a symbolic link. The threat model includes an attacker who is not granted full filesystem access by a hosting provider, but can reconfigure the home directory of an FTP user.

Upstream patch (1.3.5 branch):

https://github.com/proftpd/proftpd/commit/ecff21e0d0e84f35c299ef91d7fda088e516d4ed

Upstream bug:

http://bugs.proftpd.org/show_bug.cgi?id=4295
Comment 1 Andrej Nemec 2017-04-06 08:10:31 EDT
Created proftpd tracking bugs for this issue:

Affects: epel-all [bug 1439696]
Affects: fedora-all [bug 1439695]
Comment 2 customercare 2017-04-19 09:12:54 EDT
The patch is buggy: See Bugreport #1443507

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