![]() |
Inicial ▼ Bookkeeping
Online ▼ Auditorias ▼
DNS
Administrado ▼
Acerca de DNS
Ordenar/Renovar
Preguntas Frecuentes
AUP
Dynamic DNS Clients
Configurar Dominios Dynamic DNS Update Password Monitoreo
de Redes ▼
Enterprise
Avanzado
Estándarr
Prueba
Preguntas Frecuentes
Resumen de Precio/Funciones
Ordenar
Muestras
Configure/Status Alert Profiles | ||
ID de Prueba: | 1.3.6.1.4.1.25623.1.0.50903 |
Categoría: | Mandrake Local Security Checks |
Título: | Mandrake Security Advisory MDKSA-2001:077-1 (apache) |
Resumen: | NOSUMMARY |
Descripción: | Description: The remote host is missing an update to apache announced via advisory MDKSA-2001:077-1. A problem exists with all Apache servers prior to version 1.3.19. The vulnerablity could allow directory indexing and path discovery on the vulnerable servers with a custom crafted request consisting of a long path name created artificially by using numerous slashes. This can cause modules to misbehave and return a listing of the directory contents by avoiding the error page. Another vulnerability found by Procheckup (www.procheckup.com) was that all directories, by default, were configured as browseable so an attacker could list all files in the targeted directories. As well, Procheckup found that the perl-proxy/management software on port 8200 would supply dangerous information to attackers due to a perl status script that was enabled. We have disabled directory browsing by default and have disabled the perl status scripts. Update: The previous updates for 7.2 had some problems with mod_perl segfaulting and with mod_ssl under 7.1. As well, ApacheJServ was not included for 7.2 and 8.0. Other security fixes were introduced in Apache 1.3.22. A vulnerability in the split-logfile support program would allow any file with a .log extension on the system to be written to due to a specially crafted Host: header. This update provides Apache 1.3.22 for all supported platforms, and the packages for 7.1, 7.2, and Corporate Server 1.0.1 now use the same modular design as 8.0 and later versions. You will be unable to safely upgrade these packages and will need to take a few very important manual steps to ensure a proper upgrade (this is only applicable to 7.2 and earlier distributions this is not required for 8.0 and later): 1) Stop apache (service httpd stop) 2) Completely backup /etc/httpd/conf/* 3) Backup /var/log/httpd (the uninstall scripts of the previous apache versions may remove the log files) 4) Remove the currently installed apache, mod_perl, mod_ssl, and php packages from the system. You can do this using: urpme apache urpme php or (if you are using 7.2): urpme apache-common urpme php 5) Upgrade mm/mm-devel and (if you are upgrading 7.1 or Corporate Server) the new perl packages 6) Install the download upgrade packages of apache components using rpm -ivh *.rpm 7) Restore your /var/log/httpd backup 8) Merge your configuration backups with the new config files (most notably you will need to edit commonhttpd.conf) 9) Start apache (service httpd start) This update also introduces PHP 4.0.6 to Linux-Mandrake 7.1, 7.2, and Corporate Server. Affected versions: 7.1, 7.2, 8.0, 8.1, Corporate Server 1.0.1 Solution: To upgrade automatically use MandrakeUpdate or urpmi. The verification of md5 checksums and GPG signatures is performed automatically for you. https://secure1.securityspace.com/smysecure/catid.html?in=MDKSA-2001:077-1 http://www.securityfocus.com/bid/2503 http://bugs.apache.org/index.cgi/full/7848 http://www.apacheweek.com/issues/01-09-28#security http://www.securityfocus.com/bid/3009 http://www.procheckup.com/vulnerabilities/pr0107.html http://www.linux-mandrake.com/en/security/RPM-GPG-KEYS Risk factor : High |
Copyright | Copyright (c) 2005 E-Soft Inc. http://www.securityspace.com |
Esta es sólo una de 146377 pruebas de vulnerabilidad en nuestra serie de pruebas. Encuentre más sobre cómo ejecutar una auditoría de seguridad completa. Para ejecutar una prueba gratuita de esta vulnerabilidad contra su sistema, regístrese ahora. |