Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. The ftp and scp tasks of Apache Ant can download files from a remote server. A malicious server can provide relative paths that allow it to write outside of the dedicated target directory for the download, making it possible to overwrite files of the attacker's choice using the permissions of the user running Ant in versions prior to Ant 1.10.18. In order to exploit this vulnerability, the server would either have to be malicious or be subject to a machine-in-the-middle attack. Additionally in the case of scp or the ftp task using ftps the server must pass the server identity checks performed by the tasks. For ftp tasks not using ftps a malicious server could act as a machine-in-the-middle to provide malicious files. Starting with Ant 1.10.18 both tasks will prevent writing outside of the destination directory by default. An option is available to disable this behavior in the unlikely case that the old behavior is required by existing build files. Mitigations: Users of scp and ftp (when using ftps) in any version of Ant should not bypass server identity checks. Users of ftp not using ftps should switch to ftps where possible. All users are recommended to upgrade to Apache Ant 1.10.18, which fixes this issue.
Not applicable to fop. This is a flaw in Apache Ant's ftp and scp task implementations. The upstream advisory scopes it to a single coordinate: "Apache Ant (org.apache.ant:ant) 1.2 before 1.10.18". The fop package does not ship Ant. It has no BuildRequires or Requires on ant, it builds with Maven rather than Ant, and %prep removes any jars shipped in the upstream source tarball: rm -f fop/lib/*.jar fop/lib/build/*.jar Checking the most recent build log confirms this — there is no Ant invocation anywhere in it. The binary package contains fop's own artifacts only, so the vulnerable FTP and Scp classes are not present. Fop does provide an Ant task of its own (org.apache.fop.tools.anttasks.Fop), which may be why this tracker was created, but that compiles against Ant's API rather than embedding it. Worth noting separately: Fedora currently ships ant-1.10.15, and this issue is fixed in Ant 1.10.18. There does not appear to be a component tracker against ant itself, although twelve packages that consume it have received one.