The following flaw was found in proftpd: Part of the SFTP handshake involves "extensions", which are key/value pairs, comprised of strings. In SSH, strings are encoded for network transport as a 32-bit length, followed by the bytes. The mod_sftp module currently places no bounds/length limitations when reading these SFTP extension key/value data from the network. A malicious attacker might attempt to encode large values, and allocate more memory than is necessary. To avoid undue resource exhaustion by a remote client, mod_sftp should place a limit on the maximum length of acceptable extension keys/values. Upstream bug: http://bugs.proftpd.org/show_bug.cgi?id=4210 Upstream patch: https://github.com/proftpd/proftpd/pull/171
Created proftpd tracking bugs for this issue: Affects: fedora-all [bug 1286978] Affects: epel-all [bug 1286979]
Is it worth waiting for a CVE number for this issue to put in the package changelog before pushing an update?
(In reply to Paul Howarth from comment #2) > Is it worth waiting for a CVE number for this issue to put in the package > changelog before pushing an update? Definitely not, I'd go ahead and push the update referencing this BZ.
proftpd-1.3.5a-5.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
proftpd-1.3.5a-5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
proftpd-1.3.5a-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
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.