Errors in both the klogd and the syslogd can cause both daemons do die when specially designed strings get passed to the kernel by the user.. -----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: syslogd/klogd Date: Wednesday, September 20th, 2000 03:00 MEST Affected SuSE versions: 6.1 6.2, 6.3, 6.4, 7.0 Vulnerability Type: local DoS, possible root compromise Severity (1-10): 5 SuSE default package: yes Other affected systems: Linux systems, possibly unix systems Content of this advisory: 1) security vulnerability resolved: syslogd/klogd problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information The syslogd package consists of two daemons that are being launched upon system startup: klogd and syslogd. The former collects kernel messages and passes them on to the syslog(3) facility. syslogd will pick up the logging messages and write them to the logfiles as specified by the syslogd configuration file /etc/syslog.conf. Errors in both the klogd and the syslogd can cause both daemons do die when specially designed strings get passed to the kernel by the user, eg. with a malformed structure in a system call. These errors have been discovered by Jouko Pynnönen, Solar Designer, a fix for one of the bugs has been provided by Daniel Jacobowitz. There is currently no known way to exploit these bugs with an effect other than a DoS (Denial of Service) of the syslog/klog service. Since it may be possible to execute arbitrary code as a result of a buffer overflow, administrators should consider applying the patches as soon as possible. Also, logging messages resulting from firewall rules in the kernel can get lost if the daemon does not pick them up. Efficient temporary countermeasures against these attacks other than package upgrade do not exist. Download the update package from locations desribed below and install the package with the command `rpm -Fhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig --nogpg file.rpm', independently from the md5 signatures below. i386 Intel Platform: SuSE-7.0 284b1975cda65cd6ed5ce65672706e19 source rpm: 49c7a171753171f4e6fd772453d46a93 SuSE-6.4 cb89ed419b0c9dbf7c66191a58606920 source rpm: 33686198aa6412401b0056241829aae0 SuSE-6.3 af5e43976fb9814e1f5d626e16c2d176 source rpm: 1e821f6fda1f471d36e9b4990aa496b4 SuSE-6.2 145f83a8b687c84c5d821db5639f2e2c source rpm: fb6800b4a5726c4d45b26e40d29af4a5 SuSE-6.1 c8d23ec6c3a9f944c15d6e12ffebc66f source rpm: b0329c20caf1d1d427da9961240732f5 SuSE-5.3 eb352b52e17db8f65ebc5ec44ff0fdb0 8a0c5626ab36581650971944f386f8c1 Sparc Platform: SuSE-7.0 38bb40e8bdfd55387f0e25407d4e5cbd source rpm: 2017cbca57305092c0a912b77c2411dd AXP Alpha Platform: SuSE-6.4 419ea3172f4532f77c4fc5907de345f2 source rpm: 44cb992c94dffff0d31b65a0938fc1cc SuSE-6.3 84cfb8fa2e471baadf96eae1d3be1d0a source rpm: 23ee4562c993de6943cead4878e73259 SuSE-6.1 3b04489436b536d3d2e4b4bec6bc5ced source rpm: ab7edad2685d8d820b0f72b470048e81 PPC Power PC Platform: SuSE-6.4 9d588d1d4614d173b60746ae74fc6046 sourcerpm: eae3b0cd9b7de4ded453e9151b722b0e ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: This is the updated list of currently known security problems. Other problems such as the one from the subject of this advisory have passed these vulnerabilities due to greater severity. - esound, xchat, gnorpm, xpdf These packages are known to exhibit file race conditions. We will provide update packages soon. - pine The pine Mail User Agent may crash when it encounters a specially crafted header line in an email. Again, we're working on a patch. ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe:
The syslogd server uses a Unix Domain stream socket (/dev/log) for receiving local log messages via syslog(3). Unix Domain stream sockets are non connection-less, that means, that one process is needed to serve one client. . _____________________________________________________________________________ SuSE Security Announcement - syslogd (a1) Package: syslogd-1.3.33 (a1) Date: Thu Nov 18 14:00:29 CET 1999 Affected SuSE versions: 6.2 and 6.3 Vulnerability Type: local denial-of-service attack SuSE default package: yes Other affected systems: all Linux systems using the syslog daemon ______________________________________________________________________________ A security hole was discovered in the package mentioned above. Please update as soon as possible or disable the service if you are using this software on your SuSE Linux installation(s). Other Linux distributions or operating systems might be affected as well, please contact your vendor for information about this issue. Please note, that that we provide this information on an "as-is" basis only. There is no warranty whatsoever and no liability for any direct, indirect or incidental damage arising from this information or the installation of the update package. _____________________________________________________________________________ 1. Problem Description The syslogd server uses a Unix Domain stream socket (/dev/log) for receiving local log messages via syslog(3). Unix Domain stream sockets are non connection-less, that means, that one process is needed to serve one client. 2. Impact By opening alot of local syslog connections a user could stop the system from responding. 3. Solution Updated the package from our FTP server. ______________________________________________________________________________ Please verify these md5 checksums of the updates before installing: c9a9e0f8fc4e29daf30f8a735ae333ab syslogd-1.3.33-9.alpha.rpm (AXP, 6.1) 3104e26a8b474e215ed703b7c4d48888 syslogd-1.3.33-9.i386.rpm (x86, 5.3) a13be12a75232f2f62f51fb1cae26fc0 syslogd-1.3.33-9.i386.rpm (x86, 6.1) fc29df9455288f40eb1e8dbd0f47d5b3 syslogd-1.3.33-9.i386.rpm (x86, 6.2) 869b7fedd5b52807f12b7f66e282002c syslogd-1.3.33-9.i386.rpm (x86, 6.3) ______________________________________________________________________________ You can find updates on our ftp-Server: or try the following web pages for a list of mirrors: https://www.suse.com/de-de/ https://www.suse.com/de-de/ Our webpage for patches: https://www.suse.com/de-de/ Our webpage for security announcements: https://www.suse.com/de-de/ If you want to report vulnerabilities, please contact
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 (okir@monad.swb.de) 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: None 6. Conflicts with: None 7. RPMs required: Intel: sysklogd-1.3.31-14.i386.rpm Source: sysklogd-1.3.31-14.src.rpm 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 thesystem 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: 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: . The latest advisory from Red Hat highlights a critical vulnerability in syslogd leading to potential denial of service attacks. A prompt upgrade is advised to bolster system security.. syslogd, Red Hat, denial of service, security patch. . LinuxSecurity.com Team
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 (okir@monad.swb.de) 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: None 6. Conflicts with: None 7. RPMs required: Intel: sysklogd-1.3.31-14.i386.rpm Source: sysklogd-1.3.31-14.src.rpm 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 thesystem 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: 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: . Red Hat's advisory warns of DoS risks with syslogd, stressing prompt patching and mitigation strategies to enhance system stability and logging integrity. Red Hat Security, Syslogd Exploit, Deny Service Attack. . Severity: Critical. LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.