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: July 28th, 2014
Linux Advisory Watch: July 25th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
RH6.1: bind (RHSA-1999:054-01) Print E-mail
User Rating:      How can I rate this item?
Posted by LinuxSecurity.com Team   
RedHat Linux Several security vulnerabilities exist in the DNS server, 'bind'.
 
Red Hat, Inc. Security Advisory
Package bind

Synopsis Security problems in bind

Advisory ID RHSA-1999:054-01

Issue Date 1999-11-11

Updated on 1999-11-11

Keywords bind named NXT solinger fdmax



1. Topic:
Several security vulnerabilities exist in the DNS server, 'bind'.

2. Problem description:
Various vulnerabilities exist in previous versions of bind:

  • A bug in the processing of NXT records can theoretically allow a remote attacker to gain access to the DNS server as the user running bind (by default, root). This vulnerability does not affect the bind packages that shipped with Red Hat Linux 4.2 and Red Hat Linux 5.2.
  • Several remote denial-of-service attacks are possible; by using abnormal TCP options, causing the DNS server to use many file descriptors, or using special SIG records, it may be possible to crash the DNS server.

    It is recommended that all users of bind upgrade to the latest packages.

    Thanks go to ISC for providing the updated packages.

    3. Bug IDs fixed: (see bugzilla for more information)

    4. Relevant releases/architectures:
    Red Hat Linux 6.1, all architectures

    5. Obsoleted by:
    None

    6. Conflicts with:
    None

    7. RPMs required:

    Intel:

    ftp://updates.Red Hat.com/6.1/i386/

    bind- 8.2.2_P3-1.i386.rpm
    bind- devel-8.2.2_P3-1.i386.rpm
    bind- utils-8.2.2_P3-1.i386.rpm

    Alpha:

    ftp://updates.Red Hat.com/6.0/alpha

    bind- 8.2.2_P3-1.alpha.rpm
    bind-devel-8.2.2_P3-1.alpha.rpm
    bind-utils-8.2.2_P3-1.alpha.rpm

    SPARC:

    ftp://updates.Red Hat.com/6.0/sparc

    bind- 8.2.2_P3-1.sparc.rpm
    bind-devel-8.2.2_P3-1.sparc.rpm
    bind-utils-8.2.2_P3-1.sparc.rpm

    Source:

    ftp://updates.Red Hat.com/6.1/SRPMS

    bind- 8.2.2_P3-1.src.rpm

    8. Solution:
    For each RPM for your particular architecture, run:

    rpm -Uvh filename

    where filename is the name of the RPM.

    Then you will want to restart the named service like so:

    /etc/rc.d/init.d/named stop
    /etc/rc.d/init.d/named start

    9. Verification:

    
     MD5 sum                           Package Name
    
     -------------------------------------------------------------------------
    f0c2e341fe81310d3031be7e0d67225f  i386/bind-8.2.2_P3-1.i386.rpm
    4f34e526ec52c94b9cd3411892f920df  i386/bind-devel-8.2.2_P3-1.i386.rpm
    5cb10493b44f9fe2a9c6667ebe0a0a8f  i386/bind-utils-8.2.2_P3-1.i386.rpm
    94e19627ae83388e7d4795f45676c4b6  alpha/bind-8.2.2_P3-1.alpha.rpm
    06932040ed8b8ff5eb8edb09c069acf9  alpha/bind-devel-8.2.2_P3-1.alpha.rpm
    de0fa8d33d877d2ed7f8d26949b4a937  alpha/bind-utils-8.2.2_P3-1.alpha.rpm
    54b757c6e240d4c82ca740ac49eb3db7  sparc/bind-8.2.2_P3-1.sparc.rpm
    8453658392c3b2a321f7647eb875d5d2  sparc/bind-devel-8.2.2_P3-1.sparc.rpm
    9894188ea1e8a5f657f13d940091114d  sparc/bind-utils-8.2.2_P3-1.sparc.rpm
    987d55828aab270e14777a034d029cea  SRPMS/bind-8.2.2_P3-1.src.rpm
     
    
     
    These packages are GPG signed by Red Hat, Inc. for security. Our key is available at:
    http://www.Red Hat.com/corp/contac t.html

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

    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 filename

    Note that you need RPM >= 3.0 to check GnuPG keys.

    10. References:


 
 
< 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
DARPA-derived secure microkernel goes open source tomorrow
Hacker Gary McKinnon turns into a search expert
Hackers seed Amazon cloud with potent denial-of-service bots
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.