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

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Advisory Watch: March 27th, 2015
Linux Security Week: March 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

RH6.0: syslogd (RHSA-1999:055-01) Print E-mail
User Rating:      How can I rate this item?
Posted by Team   
RedHat Linux A denial of service attack exists in the system log daemon, syslogd.
Red Hat, Inc. Security Advisory
Package syslogd

Synopsis Denial of service attack in syslogd

Advisory ID RHSA-1999:055-01

Issue Date 1999-11-19

Updated on 1999-11-19

Keywords syslogd sysklogd stream socket

Cross References bugtraq id #809

1. Topic:
A denial of service attack exists in the system log daemon, syslogd.

2. Problem description:
The syslog daemon by default used unix domain stream sockets for receiving local log connections. By opening a large number of connections to the log daemon, the user could make the system unresponsive.

Thanks go to Olaf Kirch ( for noting the vulnerability and providing patches.

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

4. Relevant releases/architectures:
Red Hat Linux 6.1:
Red Hat Linux 6.1 is not vulnerable to this security issue. However, users of Red Hat Linux 6.1/Intel may wish to upgrade to the latest package to fix a problem in the syslog daemon where log connections would be reset after the syslog daemon is restarted.

5. Obsoleted by:

6. Conflicts with:

7. RPMs required:







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

rpm -Uvh filename

where filename is the name of the RPM.

libc updates are needed for Red Hat Linux 4.2 for the Intel and Sparc architectures so that logging will work correctly with the upgraded sysklogd packages.

Note: Upgrading to these sysklogd packages may impair the logging abilities of some software that does not use the standard C library syslog(3) interface to the system logs. Such software may have to be changed to use datagram connections instead of stream connections to the log socket.

9. Verification:

 MD5 sum                           Package Name

8e59b61b8b1a9356ea675d7234b801d8  i386/sysklogd-1.3.31-14.i386.rpm
55cc22adb6b3272ef23763e89309af24  SRPMS/sysklogd-1.3.31-14.src.rpm

These packages are GPG signed by Red Hat, Inc. for security. Our key is available at:
http://www.Red 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 >


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
Weekend Edition
FBI Quietly Removes Recommendation To Encrypt Your Phone
And the prize for LEAST SECURE BROWSER goes to ... Chrome!
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 2015 Guardian Digital, Inc. All rights reserved.