Red Hat Security Advisory: : Updated secureweb packages available
Updated packages are now available for Red Hat Secure Web Server 3.2 (U.S.). These updates close a potential security hole which would present clients with a listing of the contents of a directory instead of the contents of an index file or the proper error message. The previous revision of this errata advisory included incorrect URLs. This revision lists the correct location of the updated packages.
describes (2)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2001-0730US | medium5.0 | — | ||
split-logfile in Apache 1.3.20 allows remote attackers to overwrite arbitrary files that end in the .log extension via an HTTP request with a / (slash) in the Host: header. | ||||
| CVE-2001-0731US | medium5.0 | Exploit | ||
Apache 1.3.20 with Multiviews enabled allows remote attackers to view directory contents and bypass the index page via a URL containing the "M=D" query string. | ||||
references
External citations — patches, advisories, analysis.
remediations (2)
- FixedRed Hat Secure Web Server 3.2
The main secureweb package is provided as an rhmask file. In order to generate the actual secureweb RPM package, you will need the secureweb-3.2-12 package file from the Secure Web Server CD. Then, using the rhmask command, generate the secureweb RPM package: rhmask secureweb-3.2-12.i386.rpm secureweb-3.2.4-1.i386.rpm.rhmask Before applying this update, make sure you have applied all previously released errata relevant to your system. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs.
https://access.redhat.com/errata/RHSA-2001:164 - FixedRed Hat Secure Web Server 3.2
The main secureweb package is provided as an rhmask file. In order to generate the actual secureweb RPM package, you will need the secureweb-3.2-12 package file from the Secure Web Server CD. Then, using the rhmask command, generate the secureweb RPM package: rhmask secureweb-3.2-12.i386.rpm secureweb-3.2.4-1.i386.rpm.rhmask Before applying this update, make sure you have applied all previously released errata relevant to your system. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs.
https://access.redhat.com/errata/RHSA-2001:164
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan