Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 508
Alerts This Week
Warning Icon 1 508

Stay Secure with the Latest Linux Advisories

Filter%20icon Refine advisories
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security advisories

We found 8 articles for you...
89

Fedora 43 PackageKit Critical Root Compromise Threat 2026-7463cd3c32

Backport fix for race condition leading to root compromise (GHSA-f55j-vvr9-69xv). -------------------------------------------------------------------------------- Fedora Update Notification FEDORA-2026-7463cd3c32 2026-04-28 00:55:52.209321+00:00 -------------------------------------------------------------------------------- Name : PackageKit Product : Fedora 43 Version : 1.3.4 Release : 3.fc43 URL : http://www.freedesktop.org/software/PackageKit/ Summary : Package management service Description : PackageKit is a D-Bus abstraction layer that allows the session user to manage packages in a secure way using a cross-distro, cross-architecture API. -------------------------------------------------------------------------------- Update Information: Backport fix for race condition leading to root compromise (GHSA-f55j-vvr9-69xv) -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 22 2026 Neal Gompa - 1.3.4-3 - Actually apply patch for security fix * Wed Apr 22 2026 Neal Gompa - 1.3.4-2 - Backport fix for GHSA-f55j-vvr9-69xv -------------------------------------------------------------------------------- References: [ 1 ] Bug #2460579 - Local Privilege escalation: Run code as root due to race condition in PackageKit https://bugzilla.redhat.com/show_bug.cgi?id=2460579 -------------------------------------------------------------------------------- This update can be installed with the "dnf" update program. Use su -c 'dnf upgrade --advisory FEDORA-2026-7463cd3c32' at the command line. For more information, refer to the dnf documentation available at http://dnf.readthedocs.io/en/latest/command_ref.html#upgrade-command-label All packages are signed with the Fedora Project GPG key. More details on the GPG keys used by the Fedora Project can be found at https://fedoraproject.org/keys -------------------------------------------------------------------------------- -- _______________________________________________ package-announce mailing list -- This email address is being protected from spambots. You need JavaScript enabled to view it. To unsubscribe send an email to This email address is being protected from spambots. You need JavaScript enabled to view it. Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/This email address is being protected from spambots. You need JavaScript enabled to view it. Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new . Fixed root compromise risk in PackageKit for Fedora 43. Ensure system security with this critical update. . Fedora PackageKit Security Update, Fedora 43 Critical Threat, Package Management Vulnerability, Root Compromise Fix. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Apr 28, 2026 Critical Fedora
91

Gentoo: GLSA-200408-15 Normal: Tomcat Insecure Installation Risk

Improper file ownership may allow a member of the tomcat group to execute scripts as root.. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Gentoo Linux Security Advisory GLSA 200408-15 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - https://security.gentoo.org/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Severity: Normal Title: Tomcat: Insecure Installation Date: August 15, 2004 Bugs: #59232 ID: 200408-15 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Synopsis ======= Improper file ownership may allow a member of the tomcat group to execute scripts as root. Background ========= Tomcat is the Apache Jakarta Project's official implementation of Java Servlets and Java Server Pages. Affected packages ================ ------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-www/tomcat < 5.0.27-r3 > = 5.0.27-r3 *> = 4.1.30-r4 *> = 3.3.2-r2 Description ========== The Gentoo ebuild for Tomcat sets the ownership of the Tomcat init scripts as tomcat:tomcat, but those scripts are executed with root privileges when the system is started. This may allow a member of the tomcat group to run arbitrary code with root privileges when the Tomcat init scripts are run. Impact ===== This could lead to a local privilege escalation or root compromise by authenticated users. Workaround ========= Users may change the ownership of /etc/init.d/tomcat* and /etc/conf.d/tomcat* to be root:root: # chown -R root:root /etc/init.d/tomcat* # chown -R root:root/etc/conf.d/tomcat* Resolution ========= All Tomcat users can upgrade to the latest stable version, or simply apply the workaround: # emerge sync # emerge -pv "> =net-www/tomcat-5.0.27-r3" # emerge "> =net-www/tomcat-5.0.27-r3" Availability =========== This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/200408-15 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 This email address is being protected from spambots. You need JavaScript enabled to view it. or alternatively, you may file a bug at https://bugs.gentoo.org/. License ====== Copyright 2004 Gentoo Foundation, Inc; referenced text belongs to its owner(s). The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license. https://creativecommons.org/licenses/by-sa/1.0/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBH4FfzKC5hMHO6rkRAjT7AJ9U2eXQGi5gGFRwokYJx2n/1Nv6mQCffn2w FKP86R2pMqASV4enpi8UOu8=FhC/ -----END PGP SIGNATURE----- . Enhance your security posture by analyzing the vulnerabilities tied to the Tomcat setup and implementing measures to prevent root access breaches on Gentoo.. Tomcat Configuration, Gentoo Advisory, Privilege Escalation Risk. . LinuxSecurity.com Team

Calendar%202 Aug 15, 2004 Gentoo
91

Gentoo: 200312-08 High: CVS Root Privilege Escalation Fix

This release adds code to the CVS server to prevent it from continuing as root after a user login, as an extra failsafe against a compromise of the CVSROOT/passwd file.. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -------------------------------------------------------------------------- GENTOO LINUX SECURITY ANNOUNCEMENT 200312-08 - -------------------------------------------------------------------------- GLSA: 200312-08 package: dev-util/cvs summary: Fix for possible root compromise when using CVS pserver severity: high Gentoo bug: 36142 date: 2003-12-28 exploit: unknown affected: =1.11.11 DESCRIPTION: Quote from

Calendar%202 Dec 29, 2003 Critical Gentoo
91

Gentoo: GLSA-200312-09 Critical Severity: FSEvents Vulnerability Patch

Quote from : "Stable CVS 1.11.11 has been released. Stable releases contain only bug fixes from previous versions of CVS. This release adds code to [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -------------------------------------------------------------------------- GENTOO LINUX SECURITY ANNOUNCEMENT 200312-08 - -------------------------------------------------------------------------- GLSA: 200312-08 package: dev-util/cvs summary: Fix for possible root compromise when using CVS pserver severity: high Gentoo bug: 36142 date: 2003-12-28 exploit: unknown affected: =1.11.11 DESCRIPTION: Quote from : "Stable CVS 1.11.11 has been released. Stable releases contain only bug fixes from previous versions of CVS. This release adds code to the CVS server to prevent it from continuing as root after a user login, as an extra failsafe against a compromise of the CVSROOT/passwd file. Previously, any user with the ability to write the CVSROOT/passwd file could execute arbitrary code as the root user on systems with CVS pserver access enabled. We recommend this upgrade for all CVS servers!" SOLUTION: All Gentoo Linux machines with cvs installed should be updated to use cvs-1.11.11 or higher. emerge sync emerge -pv '> =dev-util/cvs-1.11.11' emerge '> =dev-util/cvs-1.11.11' emerge clean // end -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQE/79SAnt0v0zAqOHYRAuWTAJ9UY/lAvsKQRtHLQZr/zDUf5eok6wCgumZt ICbAjuPbALouwsdG16pqS6s=UQlf -----END PGP SIGNATURE----- . Upgrade CVS to version 1.11.11 in order to address critical root compromise vulnerabilities on Gentoo setups.. Gentoo security, CVS update, root compromise, high severity advisory. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Dec 29, 2003 Critical Gentoo
98

Red Hat Linux: RHSA-2002:011-06 Critical: Sudo Local Access Exploit

Versions of sudo prior to 1.6.4 would not clear the environment beforesending an email notification about unauthorized sudo attempts, making itpossible for an attacker to supply parameters to the mail program.. ` --------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: Updated sudo packages are available Advisory ID: RHSA-2002:011-06 Issue date: 2002-01-14 Updated on: 2002-01-15 Product: Red Hat Linux Keywords: sudo environment Cross references: Obsoletes: --------------------------------------------------------------------- 1. Topic: Updated sudo packages fixing a security problem are available. 2. Relevant releases/architectures: Red Hat Linux 7.0 - alpha, i386 Red Hat Linux 7.1 - alpha, i386, ia64 Red Hat Linux 7.2 - i386, ia64 3. Problem description: Versions of sudo prior to 1.6.4 would not clear the environment before sending an email notification about unauthorized sudo attempts, making it possible for an attacker to supply parameters to the mail program. In the worst case, this could lead to a local root exploit. Users of sudo are advised to upgrade to version 1.6.4 which is not vulnerable to 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 following command: up2date This will start aninteractive process that will result in the appropriate RPMs being upgraded on your system. 5. Bug IDs fixed ( for more info): 6. RPMs required: Red Hat Linux 7.0: SRPMS: alpha: i386: Red Hat Linux 7.1: SRPMS: alpha: i386: ia64: Red Hat Linux 7.2: SRPMS: i386: ia64: 7. Verification: MD5 sum Package Name -------------------------------------------------------------------------- 68dfd955e1e8f39fe41a4b7639195f11 7.0/en/os/SRPMS/sudo-1.6.4-0.7x.2.src.rpm ff225f9d53084e29d0d558c8daea95b6 7.0/en/os/alpha/sudo-1.6.4-0.7x.2.alpha.rpm ca088e51c3dd8f172063b0f8d122a5e5 7.0/en/os/i386/sudo-1.6.4-0.7x.2.i386.rpm 68dfd955e1e8f39fe41a4b7639195f11 7.1/en/os/SRPMS/sudo-1.6.4-0.7x.2.src.rpm ff225f9d53084e29d0d558c8daea95b6 7.1/en/os/alpha/sudo-1.6.4-0.7x.2.alpha.rpm ca088e51c3dd8f172063b0f8d122a5e5 7.1/en/os/i386/sudo-1.6.4-0.7x.2.i386.rpm fedccbb28833f82f220ab148fb2cd42a 7.1/en/os/ia64/sudo-1.6.4-0.7x.2.ia64.rpm 68dfd955e1e8f39fe41a4b7639195f11 7.2/en/os/SRPMS/sudo-1.6.4-0.7x.2.src.rpm ca088e51c3dd8f172063b0f8d122a5e5 7.2/en/os/i386/sudo-1.6.4-0.7x.2.i386.rpm fedccbb28833f82f220ab148fb2cd42a 7.2/en/os/ia64/sudo-1.6.4-0.7x.2.ia64.rpm These packages are GPG signed by Red Hat, Inc. for security. Our key is available at: About 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: Sudo Manual | Sudo Copyright(c) 2000, 2001, 2002 Red Hat, Inc. `. Recent enhancements to sudo components have been introduced to address local privilege escalation weaknesses resulting from illicit email notifications found in earlier iterations.. Red Hat Advisory,Sudo Exploit,Update Security,Local Access Rights,Root Privilege Escalation. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jan 15, 2002 Critical Red Hat
100

SuSE: SA:2001:028 Moderate: Local Root Exploit in Sendmail

Cade Cairns of Securityfocus discovered a vulnerability in the sendmail program, the widely spread MTA used in Unix- and Unix-like systems.. ______________________________________________________________________________ SuSE Security Announcement Package: sendmail Announcement-ID: SuSE-SA:2001:028 Date: Thursday, Aug 23rd 2001 18:10 MEST Affected SuSE versions: 7.0, 7.1, 7.2 Vulnerability Type: local root compromise Severity (1-10): 5 SuSE default package: yes Other affected systems: systems using the sendmail package Content of this advisory: 1) security vulnerability resolved: sendmail 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 Cade Cairns of Securityfocus discovered a vulnerability in the sendmail program, the widely spread MTA used in Unix- and Unix-like systems. A local user can write arbitrary data to the process memory, resulting in user-controlled code to be executed as user root. Please note that this is a _local_ vulnerability: Local shell access is needed for the attacker to be able to take advantage of this error. The /usr/sbin/sendmail program is installed set-uid root in most installations. This special privilege is needed for the sendmail program to operate properly. The attack pattern involves running sendmail to make use of the setuid-bit. Please note that this is the first sendmail security problem since 1997. In this case, the vulnerability can be classified as a commandline processing bug while running with extended (root) privilege. The error itself is a result of a comparison betweena signed and an unsigned integer when checking user-supplied data from the sendmail command line: A high unsigned value is being considered a negative signed value. A subsequent comparison is being evaluated the wrong way. These errors are expected to make up a new class of vulnerabilities for programs written in C in the near future. The supported SuSE Linux distributions 6.3 and 6.4 use a sendmail of version 8.9.3. According to Sendmail Inc., this version is not affected by this signedness bug. The SuSE Linux distributions 7.0, 7.1 and 7.2 use sendmail version 8.11.x. All 7.x distributions are affected by the problem. SuSE provides update packages for the affected distributions. Please download the update package for your distribution and use the command 'rpm -Uhv file.rpm' to apply the update. It is recommended to stop the running sendmail process(es) before applying the update. Use the command 'rcsendmail stop' to do this, and 'rcsendmail start' to restart the service after the update has been applied. Since the update packages only fix the security problem from this announcement, no reconfiguration should be necessary. SPECIAL INSTALL INSTRUCTIONS: The sendmail package needs one out of two commands to be executed after package installation. Use the commands SuSEconfig or, alternatively (if you have disabled SuSEconfig in /etc/rc.config), chkstat -set /etc/permissions.d/sendmail to set the permissions of the sendmail package files correctly. Without these permission changes, the /usr/sbin/sendmail program will not operate properly. (Side note: All of the commands above have to be run as root!) i386 Intel Platform: SuSE-7.2 edffc3231b74858c218e540ffb37740a SuSE-7.2 6a99faaaf394ab7b6dd22d9d81fb221b source rpm: e914fef1f5fb1c65bb7b52383f9832db SuSE-7.1 6cf817fe71a07fc58d4b201df01291b5 SuSE-7.1 d96f3e373f7c628d5792a2567e02e4c3 source rpm: 35c53244eafc645d4d9218d95c4f6d71 SuSE-7.0 29250e9986dfd22c7bdf637ac5dcc646 source rpm: 13153a10c4223450119d2bd57178b8d4 Sparc Platform: SuSE-7.1 08b83155a16e86bf0b41596b66115443 SuSE-7.1 3d0b567682df307f13e552b4f85b798b source rpm: a67beda92d8cbae62e8d69b263970108 SuSE-7.0 17c9c5ce0814ee9821d7646d7ea399de source rpm: d737219fb680f990d52faff49d53a48f AXP Alpha Platform: SuSE-7.1 6b7729f0c2b5dde8abb55102310bc039 SuSE-7.1 c49dd3298689e2247a5228dfb3022949 source rpm: bfa6c0c95baa236cebcf501e4efdb0e9 PPC Power PC Platform: SuSE-7.1 1ad2a5891a03cffd33baab76d0aed4f9 SuSE-7.1 b1181efdc649f005bc4a2b3fce08d164 source rpm: 4caafc40ff5332dab46cc60e3f2a85fb SuSE-7.0 27d5ac4d6d809a1ae88cf6a3fefe1d64 source rpm: f6600b2aac4d3f8356494a3d047c72f9 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions, Workarounds and misc: - ftp server Our ftp server ftp.suse.com has been reorganized. The changes in particular are: * The discontinued distributions (SuSE Linux before (and including) 6.2) have moved to an own tree: /pub/suse/discontinued/ . The tree there is built exactly like the tree for the currently supported distributions (6.3 and up). This change has been made to keep users from automatically applying updates against old problems that have been superceded by newer updates which are not available for the discontinued distributions. * The /pub/suse/ /{KDE,KDE2,GNOME,X} directories have been moved to an own tree: /pub/suse/ /supplementary/. The KDE directory has become famous in the KDE scene because it contains the latest KDE packagescompiled for a SuSE distribution. This has been done to point out that the packages in this directory have been built for the respective distribution, they are tested ok, but since these packages have never been part of the distribution they are built for, there is no support for them; the packages are provided as-is. * During the next days, all packages under the /pub/suse/ /update/ tree will be gpg-signed with the This email address is being protected from spambots. You need JavaScript enabled to view it. DSA key (see section 3 of this announcement). Currently, most of the formerly existing directories that have been moved are now still visible through a symlink, pointing at a directory with a README. The directory paths to the update packages for the supported distributions have _not_ changed. We kindly request mirror admins to adopt the changes to their trees. If you run a publically accessible mirror of ftp.suse.com, you are invited to send a mail to This email address is being protected from spambots. You need JavaScript enabled to view it. so that you are being notified of such changes in advance. - in.telnetd A buffer overflow vulnerability has been found in the in.telnetd telned daemon, a service that is enabled by default in all SuSE Linux distributions. The vulnerability may allow a remote attacker to gain root access to your system. Many unix- and unix-like operating systems are affected by this or a similar problem. There are update packages for the SuSE Linux distributions 7.1 and 7.2 on our ftp server. The packages for the 7.1 distribution are called "nkitserv", for the 7.2 distributions, the name is telnet-server. For completeness, we also provide the other packages that are made from the same source rpm. Since these packages do not fix a security problem, there is no reason to list them here. We are working on a suitable solution for the 7.0 and 6.x distributions, while it has turned out that a fix for these distributions is non-trivial because a different code base has been used for these packages. telnet is an unencrypted protocol that offers many attack possibilities. If at all possible, please deactivate your telnetd by commenting it out in /etc/inetd.conf (killall -HUP inetd afterwards to make inetd reload its configuration file!). We recommend to use one of the two ssh implementations on our distributions as a substitute of the telnet protocol. Clients are available on the internet for most platforms and operating systems. An announcement will be released soon that addresses the problem in in.telnetd. - Yesterday (Wednesday, 20010822) Bob Vickers (Dept of Computer Science, University of London) reported a locally exploitable security hole in the script /etc/init.d/boot. The critical function of the script is supposed to remove files from the defined temporary directories of the system as specified in /etc/rc.config (TMP_DIRS_TO_CLEAR in /etc/rc.config) if $CLEAR_TMP_DIRS_AT_BOOTUP (also from /etc/rc.config) is set to "yes". Unfortunately, the script does not take into account that directories can contain newlines and other non-standard characters. By consequence, the script can be tricked to removing files elsewhere. This bug is present in the SuSE Linux 7.2 version only, available for the Intel i386 platform. The feature responsible for this bug is disabled by default in a SuSE Linux 7.2 installation and must be manually activated for the bug to impose any risk. We have fixed the problem in an update package that is available at Please download and install the update package using the command rpm -Uhv aaa_base-2001.8.23-0.i386.rpm Disregard the messages on standard output if you have the gpg package installed: The postinstall script adds the DSA key This email address is being protected from spambots. You need JavaScript enabled to view it. to root's gpg public keyring if this hasn't been done already. This key is also listed below. A source rpm is also available at the usual location. We will not issue a dedicated security announcement for thisproblem. We thank Bob Vickers for reporting the problem to This email address is being protected from spambots. You need JavaScript enabled to view it.. - openssl A weakness was found in the PRNG (Pseudo Random Number Generator) of the openssl package. As far as we could determine, the bug has no effect on the packages that are compiled against a library from the openssl package. We will however provide update packages that fix the found problems. Since openssl packages are not (backwards-) compatible to any other newer version, we have to fix the package for each distribution seperately. This takes some time. A special announce- ment will be issued as soon as all packages are available. - more announcements are in our queue. Please keep watching activity on the This email address is being protected from spambots. You need JavaScript enabled to view it. mailinglist (more information below). ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key This email address is being protected from spambots. You need JavaScript enabled to view it. ), the checksums show proof of the authenticity of the package. Wedisrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig to verify the signature of the package, where is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key " This email address is being protected from spambots. You need JavaScript enabled to view it. " upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at . - SuSE runs two security mailing lists to which any interested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. Tosubscribe, send an email to . This email address is being protected from spambots. You need JavaScript enabled to view it. - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to . For general information or the frequently asked questions (faq) send mail to: or respectively. ================================================== SuSE's security contact is . The public key is listed below. ==================================================______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see The GNU Privacy Guard mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA==rVRn -----END PGP PUBLIC KEY BLOCK----- . ______________________________________________________________________________ SuSE Security Announc. cairns, securityfocus, vulnerability, sendmail, program, widely, spread. . Severity: Important. LinuxSecurity.com Team

Calendar%202 Aug 23, 2001 Important SuSE
100

SUSE: SA-2001:021 Severe: Samba Remote Access Risk Exploit

Michal Zalewski discovered that a remote attacker can write to files owned by root if the samba config file /etc/smb.conf contains the %m macro to specify the logfile for logging access to the samba server.. ______________________________________________________________________________ SuSE Security Announcement Package: samba Announcement-ID: SuSE-SA:2001:021 Date: Friday, Jun 29th 2001 14:45 MEST Affected SuSE versions: (6.0, 6.1, 6.2) 6.3, 6.4, 7.0, 7.1, 7.2 Vulnerability Type: possible remote root compromise Severity (1-10): 7 SuSE default package: yes Other affected systems: systems using samba and the %m macro in the samba main config file Content of this advisory: 1) security vulnerability resolved: samba 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 Michal Zalewski discovered that a remote attacker can write to files owned by root if the samba config file /etc/smb.conf contains the %m macro to specify the logfile for logging access to the samba server. The %m macro substitutes the NetBIOS name - improper validation of this name allows an attacker to write to any file in the system. SuSE Linux distributions do not ship a default /etc/smb.conf config file that contains the %m macro. Therefore, SuSE distributions are not vulnerable to the bug in the out-of-the-box state. In addition to the remotely exploitable bug, there exists another vulnerability which is fixed with the update packages we provide below: temporary files are being handled insecurely so that an attacker withlocal access to the system can increase her privileges. This error was discovered by Marcus Meissner, Caldera. This specific problem has been fixed with the release of the samba-2.0.9 version. samba release version 2.0.8 intended to correct this local problem, but due to an error, 2.0.9 contained the complete fix. Only the 2.0.10 version as offered for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 fixes all known problems in the samba package. For the recently released SuSE-7.2 distribution we provide an update package to the version 2.2.0a. We thank Martin Walter, CC university of Freiburg, for his helpful contribution in debugging the Large File Support (LSF) of the 7.1 package. NOTES: * We have removed the samba packages from the update trees for the 6.0, 6.1 and 6.2 distributions on our ftp-server. These packages would introduce security risks if installed on a host. * The samba source rpm package in distributions after and including 7.0 generates both the samba.rpm and the smbclnt.rpm package. It is recommended to update both packages for these distributions. Please download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3 of this security announcement. Use the command 'rpm -Uhv file.rpm' to apply the update. Special installation instructions: ================================== After successful installation of the update package, it is necessary to restart the samba server. To do this, use the following command rcsmb restart as root. i386 Intel Platform: SuSE-7.2 d0cab6f5d34645dc9e41f2ae0aed8a30 aba5da72a8175c2119e82d01184dd320 source rpm: 243964fad8bda61039020acf7a13858f SuSE-7.1 da1232db9259196a58e7e3b46065e8c8 a497089893fd375986ab5a031eddaf05 source rpm: 07705a9cacb7f9f28b434a1e6a6fe3bb SuSE-7.0 a20a0241fad9b3381758946e9f9ae16d c0194e29ff9f6ae5da8500f6a6250bab source rpm: e412b83bbf653023cadbf163a3ec296f SuSE-6.4 e740834c08f1a91efed8abfe1ffd1fd1 source rpm: ed22708ec5fbc14cfdfc0cd45b3033e0 SuSE-6.3 da6aeaf7043bc03199e4c1d5c04d3be6 source rpm: 84e325fc575143a576c42f386c88e44c Sparc Platform: SuSE-7.1 5b702a797836de3352c96b0b33297d13 00c29e2ff26d00b60a81e095a78623c7 source rpm: 1d9d41cfeab79ef851cb4666a0259731 SuSE-7.0 48ef896322723e4247b13db719a6d593 fdacfbe34e46919515dc54d288b6e56a source rpm: b023db5df4e6b26ed8263d61de3c9915 AXP Alpha Platform: SuSE-7.1 3302ca10f2e779ff168d44bc4280158a 440ff9a0fefb54ac85977e4598e39eed source rpm: 49f109c06957f200cd5112dc872273fc SuSE-7.0 6e68f4d9156238874755bd9bac59d713 c1935910e75c956ed8b2ce9e4c324d55 source rpm: 210dde7e938ff7d1d303e80a13d11673 SuSE-6.4 9d6cf089b447ba4aefe1d70cf2771a22 source rpm: 377b183857e179772481840caffd7db4 SuSE-6.3 e4871d1a0423bec9999fde9a9b85ab23 source rpm: 51cf42a086a4a26619323311660dbfb8 PPC Power PC Platform: SuSE-7.1 dfaa395540e2e01b3ccc7177f0f297c4 ca9059bfbafe4553ae6bc79dad70ce31 source rpm: df603b78073673c7f8988639b1cb2c1e SuSE-7.0 65b2d0e71902afb4f3cafa67f2d5c628 a1de2eb26df810831f65af2feb0f12f9 source rpm: 17777fa091391825ebd9d90018f950bf SuSE-6.4 4e44aaab59f3c624e77b83bbbc05bb18 source rpm: 5893c01a4f1ddf8f8d2e77ac8ee785e9 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - Location of update packages onftp.suse.de/ftp.suse.com: Licensing problems as well as US crypto-software export regulations keep us from publishing update packages that contain cryptographical software on ftp.suse.com, our US ftp server. Bandwith requirements keep us from moving the server to our German location. For these reasons, crypto-packages for SuSE Linux distributions before SuSE-7.1 can be obtained from the equivalent tree on ftp.suse.de. Distributions after and including SuSE-7.1 have their crypto-packages hosted on ftp.suse.com. This was possible with some efforts to remove all non-free cryptographical algorithms from our packages. - qpopper In our last security announcement (SuSE-SA:2001:020 gpg/gnupg) we announced that we investigate the buffer overflow that has been found in qpopper versions before 4.0.3. SuSE Linux distributions are not affected by this bug because a different version is being used. - dqs This email address is being protected from spambots. You need JavaScript enabled to view it. has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). Packages for most of the supported SuSE Linux distributions are available at the usual location / for download and installation/update. Do not forget to change the files /etc/permissions* to remove the suid-bit from the dsh program. Please note that we will not issue a dedicated security announcement for this specific bug. - pcp Paul Starzetz discovered a security weakness in the setuid root program /usr/share/pcp/bin/pmpost. The common library in pcp trusts the environment that has been supplied by the user, regardless of privileged execution or not. By consequence, a user can specify the configuration file and therefore write to files owned by root. The problem is not based on insecurely following symlinks as stated by Paul Starzetz. The pcp package is not installed by default in SuSE Linux distributions. We have provided update packages for the SuSE Linux distributions version 7.1 and 7.2 that remove the setuid bit from the pmpost binary. Versions before SuSE-7.1 were not affected because the setuid bit was not set. We thank Keith Owens and Mark Goodwin from Silicon Graphics for responding quickly and for publishing a new version of the pcp package which will be included in future releases of the SuSE Linux distribution. For more information see the /usr/share/doc/packages/pcp directory of your SuSE Linux installation after installing the update package, or go to obtained from . Please note that there will not be a dedicated security announcement for this specific bug. - xinetd A buffer overflow has been found in xinetd, all versions, all SuSE Linux distributions. It may be abused to remotely attack a host running xinetd. The xinetd package is not installed by default in SuSE Linux distributions. Manual interaction must have been applied to run the daemon. Update packages can be found at the usual location on our ftp server. The security announcement for this security problem is underway. - fetchmail (fetchml) New fetchmail packages are available on the ftp server. The packages cure a buffer overflow that can be exploited by sending a victim a specially designed email, waiting for the victim's fetchmail program to pick up the email. We are preparing a security announcement for this problem. - openssh update packages for the openssh package after (and including) SuSE-6.4 are available on our ftp servers ftp.suse.de (for = 7.1). We are currently checking for a non-security related irregularity in sshd's behaviour under faulty setup conditions. - exim SuSE Linux distributions do not contain the exim Mail Transport Agent (See Exim Internet Mailer for details) and are therefore not susceptible to the recently found security-related bugs. - webmin SuSE Linux distributions do not contain the webmin administration web frontend (See / for details) and are therefore not vulnerable to the recently found security-related problems in the software. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or rpm package: 1) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum after you downloaded the file from a SuSE ftp server or its mirrors. Then, compare the resulting md5sum with the one that is listed in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key This email address is being protected from spambots. You need JavaScript enabled to view it. ), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2)rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm -v --checksig to verify the signature of the package, where is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.gnupg/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key " This email address is being protected from spambots. You need JavaScript enabled to view it. " upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at . - SuSE runs two security mailing lists to which any interested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to . This email address is being protected from spambots. You need JavaScript enabled to view it. - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to . For general information or the frequently asked questions (faq) send mail to: or respectively. ================================================== SuSE's security contact is . The public keyis listed below. ==================================================______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the cleartext signature shows proof of the authenticity of the text. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see The GNU Privacy Guard mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA==rVRn -----END PGP PUBLIC KEY BLOCK----- . SUSE Samba advisory discusses remote access risk potentially impacting root files. Update recommended to protect systems.. Samba Security, Remote Access, Root Issue, Configuration Flaw. . LinuxSecurity.com Team

Calendar%202 Jun 29, 2001 SuSE
100

SuSE: 2001:05 Moderate Update: Cups Local Escalation Risk

A SuSE-internal security audit of the cups package conducted by Sebastian Krahmer and Thomas Biege revealed several overflows as well as insecure file handling.. ______________________________________________________________________________ SuSE Security Announcement Package: cups Announcement-ID: SuSE-SA:2001:05 Date: Monday, March 5th, 2001 13:10:13 MET Affected SuSE versions: 7.1 Vulnerability Type: local/remote root compromise Severity (1-10): 5 SuSE default package: no Other affected systems: All UN*X-systems using cups < 1.1.6. Content of this advisory: 1) security vulnerability resolved: cups 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 CUPS is an implementation of the Internet Printing Protocol (IPP) and is used as an alternative to the lpr and LPRng packages. The CUPS package aims to be a comprehensive printing solution for UN*X-systems. In SuSE-7.1 distribution, the cups package is not used by any configuration utilities unless the admin has decided to configure the package manually. The cups package has been introduced in the SuSE-7.1 distribution; enhanced support for future releases of the SuSE Linux distribution is planned. A SuSE-internal security audit conducted by Sebastian Krahmer and Thomas Biege revealed several overflows as well as insecure file handling. These bugs have been fixed by adding length-checks and securing the file-access. For a temporary workaround, remove the suid-bit from the 'lppasswd' program. Make sure nobody from outside your network can access theCUPS-server running on port 631. Allowing access to this port from outside is a bad idea regardless whether or not the used version is vulnerable. No remote-exploits are known yet. Download the update package from locations desribed below and install the package with the command `rpm -Uhv 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.1 23c6484952ab0c1de81e2db38bcd3afc SuSE-7.1 812e0c47dcfe508eb9e8ccb38165b6d7 source rpm: 204cea2ad6a61293c191e70a2cacdc82 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: Effective Monday, March 19 2001, five weeks after the release of the new SuSE-7.1 distribution, SuSE will discontinue support for the SuSE-linux distributions SuSE-6.0 SuSE-6.1 and SuSE-6.2. SuSE puts much effort into adding security improvements (patches) to the software instead of publishing a new version; the same program with a fix for a specific problem promises to work just as reliable as the original version from the distribution, whereas new versions introduce new functionality which changes the behaviour. In some cases however, especially if the security leak is based on problematic design decisions or when the fix(es) are fairly large, the only reasonable fix for a security problem is to update to a newer version of the software. These newer versions tend to become incompatible with our older distribution releases because of missing features in the operating system environment. This forces us to focus on the distributions of a newer release date. The remaining distributions SuSE-6.3, SuSE-6.4, SuSE-7.0 and SuSE-7.1 for the Intel i386,AXP Alpha, SPARC as well as PPC Power PC platforms will continue to be supported for a two-year period after the release of the respective distribution. ______________________________________________________________________________ 3) standard appendix: SuSE runs two security mailing lists to which any interested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to . This email address is being protected from spambots. You need JavaScript enabled to view it. - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to . For general information or the frequently asked questions (faq) send mail to: or respectively. ============================================== SuSE's security contact is . ============================================== Regards, Sebastian Krahmer ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048/3D25D3D9 1999/03/06 SuSE Security Team -----BEGIN PGP PUBLIC KEY BLOCK----- Version:2.6.3i mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12Cg==pIeS -----END PGP PUBLIC KEY BLOCK----- . Patches released for the CUPS package addressing security risks that could lead to local escalations on SuSE systems.. cups vulnerabilities, SuSE security, Linux printing security, root compromise, security audit. . LinuxSecurity.com Team

Calendar%202 Mar 05, 2001 SuSE
News Add Esm H240

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200