LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Security Week: October 20th, 2014
Linux Advisory Watch: October 17th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
RedHat: 'secureweb' directory listing vulnerability Print E-mail
User Rating:      How can I rate this item?
Posted by LinuxSecurity.com Team   
RedHat Linux These updates close a potential security hole which would present clientswith a listing of the contents of a directory instead of the contents of anindex file or the proper error message.

---------------------------------------------------------------------
                   Red Hat, Inc. Red Hat Security Advisory

Synopsis:          Updated secureweb packages available
Advisory ID:       RHSA-2001:164-08
Issue date:        2001-12-05
Updated on:        2001-12-07
Product:           Red Hat Secure Web Server
Keywords:          secureweb directory listing
Cross references:  RHSA-2001:126
Obsoletes:         RHBA-2000:020
---------------------------------------------------------------------

1. Topic:

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.

2. Relevant releases/architectures:

Red Hat Secure Web Server 3.2 - i386

3. Problem description:

By using a carefully constructed HTTP request, a server with
mod_negotiation and either mod_dir or mod_autoindex loaded could be tricked
into displaying a listing of the contents of a directory, despite the
presence of an index file.

The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the names CAN-2001-0730, and CAN-2001-0731 to these issues.

4. Solution:

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.

5. Bug IDs fixed  (http://bugzilla.Red Hat.com/bugzilla for more info):



6. RPMs required:

Red Hat Secure Web Server 3.2:

i386: 
ftp://updates.Red Hat.com/3.2/en/secureweb/i386/secureweb-3.2.4-1.i386.rpm.rhmask 
ftp://updates.Red Hat.com/3.2/en/secureweb/i386/secureweb-devel-3.2.4-1.i386.rpm 
ftp://updates.Red Hat.com/3.2/en/secureweb/i386/secureweb-manual-3.2.4-1.i386.rpm



7. Verification:

MD5 sum                          Package Name
--------------------------------------------------------------------------
3097ba872708a54b64354a54a3e38771 3.2/en/secureweb/i386/secureweb-3.2.4-1.i386.rpm.rhmask
93f2a1bbe394454bf35c665b5ceebddf 3.2/en/secureweb/i386/secureweb-devel-3.2.4-1.i386.rpm
f819ce00eea66d0524cba6f92c7a661e 3.2/en/secureweb/i386/secureweb-manual-3.2.4-1.i386.rpm
 

These packages are GPG signed by Red Hat, Inc. for security.  Our key
is available at:
     http://www.Red Hat.com/about/contact/pgpkey.html

You can verify each package with the following command:
    rpm --checksig  

If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
    rpm --checksig --nogpg 

8. References:
 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2001-0730 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2001-0731 
http://www.apacheweek.com/issues/01-10-05#security 
http://httpd.apache.org/dist/httpd/CHANGES_1.3 
http://www.securityfocus.com/bid/3009


Copyright(c) 2000, 2001 Red Hat, Inc.





 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Hacker Halted 2014: Johnny Long Calls for Hackers for Charity Volunteers
RIPS – Static Source Code Analysis For PHP Vulnerabilities
Finding a Video Poker Bug Made These Guys Rich—Then Vegas Made Them Pay
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.