Описание
ELSA-2010-0585: lftp security update (MODERATE)
[3.7.11-4.el5_5.3]
- Related: CVE-2010-2251 - document change of xfer:clobber default value in manpage, respect xfer:clobber on with xfer:auto-rename on (old behaviour)
[3.7.11-4.el5_5.2]
- Related: CVE-2010-2251 - describe new option xfer:auto-rename which could restore old behaviour in manpage
[3.7.11-4.el5_5.1]
- Resolves: CVE-2010-2251 - multiple HTTP client download filename vulnerability (#617870)
Обновленные пакеты
Oracle Linux 5
Oracle Linux ia64
lftp
3.7.11-4.el5_5.3
Oracle Linux x86_64
lftp
3.7.11-4.el5_5.3
Oracle Linux i386
lftp
3.7.11-4.el5_5.3
Связанные CVE
Связанные уязвимости
The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the destination filename of a download, which allows remote servers to create or overwrite arbitrary files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a dotfile in a home directory.
The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the destination filename of a download, which allows remote servers to create or overwrite arbitrary files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a dotfile in a home directory.
The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the destination filename of a download, which allows remote servers to create or overwrite arbitrary files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a dotfile in a home directory.
The get1 command, as used by lftpget, in LFTP before 4.0.6 does not pr ...
The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the destination filename of a download, which allows remote servers to create or overwrite arbitrary files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a dotfile in a home directory.