Ubuntu security team noted after extensive testing that DLA-3495-1 was incomplete as one PoC for CVE-2022-2400 (particularly the chroot escape) was still working on the patched version of the package. . - ------------------------------------------------------------------------- Debian LTS Advisory DLA-3495-2
Low: libcap security and bug fix update. Date: Thu, 8 Dec 2011 17:08:55 -0600 Reply-To:
Syslog-ng does not properly initialize its chroot jail allowing for an escape if a separate vulnerability in Syslog-ng is exploited.. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Gentoo Linux Security Advisory GLSA 200907-10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - https://security.gentoo.org/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Severity: Low Title: Syslog-ng: Chroot escape Date: July 12, 2009 Bugs: #247278 ID: 200907-10 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Synopsis ======= Syslog-ng does not properly initialize its chroot jail allowing for an escape if a separate vulnerability in Syslog-ng is exploited. Background ========= Syslog-ng is a flexible and scalable system logger. Affected packages ================ ------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 app-admin/syslog-ng < 2.1.3 *> = 2.0.10 > = 2.1.3 Description ========== Florian Grandel reported that Syslog-ng does not call chdir() before chroot() which leads to an inherited file descriptor to the current working directory. Impact ===== A local attacker might exploit a separate vulnerability in Syslog-ng and use this vulnerability to escape the chroot jail. Workaround ========= There is no known workaround at this time. Resolution ========= All Syslog-ng 2.0 users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose "> =app-admin/syslog-ng-2.0.10" All Syslog-ng 2.1 users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose "> =app-admin/syslog-ng-2.1.3" References ========= [ 1 ] CVE-2008-5110 https://www.cve.org/CVERecord?id=CVE-2008-5110 Availability =========== This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/200907-10 Concerns? ======== Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us. Any security concerns should be addressed to
Updated cvs packages that fix a client vulnerability that could be exploited by a malicious server are now available.. Red Hat Security Advisory Synopsis: Updated CVS packages fix security issue Advisory ID: RHSA-2004:154-01 Issue date: 2004-04-14 Updated on: 2004-04-14 Product: Red Hat Linux Keywords: Cross references: Obsoletes: RHSA-2004:003 CVE Names: CAN-2004-0180 - --------------------------------------------------------------------- 1. Topic: Updated cvs packages that fix a client vulnerability that could be exploited by a malicious server are now available. 2. Relevant releases/architectures: Red Hat Linux 9 - i386 3. Problem description: CVS is a version control system frequently used to manage source code repositories. Sebastian Krahmer discovered a flaw in CVS clients where rcs diff files can create files with absolute pathnames. An attacker could create a fake malicious CVS server that would cause arbitrary files to be created or overwritten when a victim connects to it. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2004-0180 to this issue. Users of CVS are advised to upgrade to these erratum packages, which contain a patch correcting this issue. 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 followingcommand: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. 5. RPMs required: Red Hat Linux 9: SRPMS: i386: 6. Verification: MD5 sum Package Name - -------------------------------------------------------------------------- 44ad2349b6b00275273280eac1a52e20 9/en/os/SRPMS/cvs-1.11.2-17.src.rpm 586d676137b75f940baa90ee28fd33ce 9/en/os/i386/cvs-1.11.2-17.i386.rpm These packages are GPG signed by Red Hat for security. Our key is available from You can verify each package with the following command: rpm --checksig -v If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: md5sum 7. References: CVE -CVE-2004-0180 8. Contact: The Red Hat security contact is . More contact details at Copyright 2004 Red Hat, Inc. . Updated CVS packages from Red Hat fix critical client exploitation risk posed by malicious servers for Linux.. Red Hat Security,cvs update,client issue,escape threat. . Severity: Critical. LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.