__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Center ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Red Hat Race Conditions in LogWatch [Red Hat RHSA-2002:053-12] April 8, 2002 16:00 GMT Number M-065 ______________________________________________________________________________ PROBLEM: Versions of LogWatch 2.1.1 and earlier have a vulnerability due to a race condition during the creation of a temporary directory. PLATFORM: Red Hat Linux 7.2 LogWatch is a customizable log analysis system which is used by default in Red Hat Linux 7.2. DAMAGE: This vulnerability can allow a local user to gain root privileges. SOLUTION: Apply the update supplied by the vendor. ______________________________________________________________________________ VULNERABILITY The risk is LOW. A local user account is needed to exploit this ASSESSMENT: vulnerability. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/m-065.shtml ORIGINAL BULLETIN: http://online.securityfocus.com/advisories/4022 ______________________________________________________________________________ [***** Start Red Hat RHSA-2002:053-12 *****] --------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: Race conditions in logwatch Advisory ID: RHSA-2002:053-12 Issue date: 2002-03-28 Updated on: 2002-04-04 Product: Red Hat Linux Keywords: logwatch tmp race Cross references: RHSA-2002:054 Obsoletes: --------------------------------------------------------------------- 1. Topic: Updated LogWatch packages are available that fix tmp file race conditions which can cause a local user to gain root privileges. 2. Relevant releases/architectures: Red Hat Linux 7.2 - noarch 3. Problem description: LogWatch is a customizable log analysis system which is used by default in Red Hat Linux 7.2. Versions of LogWatch 2.1.1 and earlier have a vulnerability due to a race condition during the creation of a temporary directory. This vulnerability can allow a local user to gain root privileges. An additional race condition was found in versions of LogWatch 2.5 and earlier. Users should update to the errata packages containing Logwatch 2.6, which are not vulnerable to these issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CAN-2002-0162 and CAN-2002-0165 to these issues. 4. Solution: Before applying this update, make sure all previously released errata relevant to your system have been applied. 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. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. 5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info): 62055 - A /tmp race condition leads to root 46371 - Handle accepted packets, not just reject and deny 56191 - logwatch is too noisy 58578 - Problem with RPM dependance 61202 - Logwatch logs appear to have emerged themselves with other logfiles. They are semi-unreadable 61829 - logwatch's sshd filter should scan secure logs 61831 - logwatch modprobe filter should allow dashes in module names 61832 - secure filter should ignore sshd messages 6. RPMs required: Red Hat Linux 7.2: SRPMS: ftp://updates.redhat.com/7.2/en/os/SRPMS/logwatch-2.6-1.src.rpm noarch: ftp://updates.redhat.com/7.2/en/os/noarch/logwatch-2.6-1.noarch.rpm 7. Verification: MD5 sum Package Name -------------------------------------------------------------------------- bb75f22ed70447d6a46d5d5b2a7ec7aa 7.2/en/os/SRPMS/logwatch-2.6-1.src.rpm ac8ea7498a2d6b14bb325a511cf8ba6b 7.2/en/os/noarch/logwatch-2.6-1.noarch.rpm These packages are GPG signed by Red Hat, Inc. for security. Our key is available at: http://www.redhat.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://list.kaybee.org/archives/logwatch-announce/2002-March/000002.html http://list.kaybee.org/archives/logwatch-announce/2002-March/000003.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0162 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0165 Copyright(c) 2000, 2001, 2002 Red Hat, Inc. [***** End Red Hat RHSA-2002:053-12 *****] _______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Red Hat, Inc. for the information contained in this bulletin. _______________________________________________________________________________ CIAC, the Computer Incident Advisory Center, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 925-422-8193 (7x24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@ciac.org Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://www.ciac.org/ Anonymous FTP: ftp.ciac.org PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) M-056: Red Hat "uuxqt" Vulnerability M-057: Red Hat "at" Vulnerability M-058: Apache Vulnerabilities on IRIX M-059: Red Hat "groff" Vulnerability M-060: JRE Bytecode Verifier Vulnerability M-061: HP VVOS Web proxy Vulnerability M-062: Double Free Bug in zlib Compression Library M-063: Microsoft Internet Explorer Vulnerabilities CIACTech02-002: Microsoft Browser Helper Objects (BHO) Could Hide Malicious Code M-064: Cisco web interface vulnerabilities in ACS for Windows