Stay Secure with the Latest Linux Advisories
Refine advisories
X Clear Filters
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
What got you started with Linux?
Loading...
Explore Latest Linux Security advisories
We found -6 articles for you...
99
security advisorysecurity issuekernel updateSlackware 15.0: 2022-129-01 Moderate: Kernel Security Threat Fix
New kernel packages are available for Slackware 15.0 to fix security issues. . -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [slackware-security] Slackware 15.0 kernel (SSA:2022-129-01) New kernel packages are available for Slackware 15.0 to fix security issues. Here are the details from the Slackware 15.0 ChangeLog: +--------------------------+ patches/packages/linux-5.15.38/*: Upgraded. These updates fix various bugs and security issues. Be sure to upgrade your initrd after upgrading the kernel packages. If you use lilo to boot your machine, be sure lilo.conf points to the correct kernel and initrd and run lilo as root to update the bootloader. If you use elilo to boot your machine, you should run eliloconfig to copy the kernel and initrd to the EFI System Partition. For more information, see: Fixed in 5.15.27: https://www.cve.org/CVERecord?id=CVE-2022-0742 https://www.cve.org/CVERecord?id=CVE-2022-24958 https://www.cve.org/CVERecord?id=CVE-2022-0494 Fixed in 5.15.28: https://www.cve.org/CVERecord?id=CVE-2022-23038 https://www.cve.org/CVERecord?id=CVE-2022-23039 https://www.cve.org/CVERecord?id=CVE-2022-23960 https://www.cve.org/CVERecord?id=CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-0001 https://www.cve.org/CVERecord?id=CVE-2022-0002 https://www.cve.org/CVERecord?id=CVE-2022-23041 https://www.cve.org/CVERecord?id=CVE-2022-23040 https://www.cve.org/CVERecord?id=CVE-2022-23042 Fixed in 5.15.29: https://www.cve.org/CVERecord?id=CVE-2022-1199 https://www.cve.org/CVERecord?id=CVE-2022-27666 https://www.cve.org/CVERecord?id=CVE-2022-1011 https://www.cve.org/CVERecord?id=CVE-2022-0995 https://www.cve.org/CVERecord?id=CVE-2022-0854 Fixed in 5.15.32: https://www.cve.org/CVERecord?id=CVE-2022-1015 https://www.cve.org/CVERecord?id=CVE-2022-26490 https://www.cve.org/CVERecord?id=CVE-2022-1048 https://www.cve.org/CVERecord?id=CVE-2022-1016 https://www.cve.org/CVERecord?id=CVE-2022-28356 Fixed in 5.15.33: https://www.cve.org/CVERecord?id=CVE-2022-28390 https://www.cve.org/CVERecord?id=CVE-2022-1158 https://www.cve.org/CVERecord?id=CVE-2022-1353 https://www.cve.org/CVERecord?id=CVE-2022-1198 https://www.cve.org/CVERecord?id=CVE-2022-28389 https://www.cve.org/CVERecord?id=CVE-2022-28388 https://www.cve.org/CVERecord?id=CVE-2022-1516 Fixed in 5.15.34: https://www.cve.org/CVERecord?id=CVE-2022-1263 https://www.cve.org/CVERecord?id=CVE-2022-29582 Fixed in 5.15.35: https://www.cve.org/CVERecord?id=CVE-2022-1204 https://www.cve.org/CVERecord?id=CVE-2022-1205 Fixed in 5.15.37: https://www.cve.org/CVERecord?id=CVE-2022-0500 https://www.cve.org/CVERecord?id=CVE-2022-23222 (* Security fix *) +--------------------------+ Where to find the new packages: +-----------------------------+ Thanks to the friendly folks at the OSU Open Source Lab (https://osuosl.org/) for donating FTP and rsync hosting to the Slackware project! :-) Also see the "Get Slack" section on http://www.slackware.com/ for additional mirror sites near you. Updated packages for Slackware 15.0: Updated packages for Slackware x86_64 15.0: MD5 signatures: +-------------+ Slackware 15.0 packages: 03a369fdb3b671e842d0f827b125ee49 kernel-generic-5.15.38-i586-1.txz 5d3ba5a7cd96835f32f4cbfe320cb793 kernel-generic-smp-5.15.38_smp-i686-1.txz ae1b1cd65c4f57458364bdcc7215af5d kernel-headers-5.15.38_smp-x86-1.txz e636240d456f26b062c43d2e1a8ba66c kernel-huge-5.15.38-i586-1.txz f958a42b87b3f518f481b6521c1e834c kernel-huge-smp-5.15.38_smp-i686-1.txz b361d0d7451a7b677e77d576e2a33241 kernel-modules-5.15.38-i586-1.txz 2e9e77cdf209636286f43628c8c41df8 kernel-modules-smp-5.15.38_smp-i686-1.txz fe913660f7d80595332ffaa5ebb5be1f kernel-source-5.15.38_smp-noarch-1.txz Slackware x86_64 15.0 packages: ef20ea1b90e3a1e2e2607d97752d2a6d kernel-generic-5.15.38-x86_64-1.txz 2d68048d011f6aa7b6757a81af093c72 kernel-headers-5.15.38-x86-1.txz b3c532fd4e07f12f511305ac81e7b32d kernel-huge-5.15.38-x86_64-1.txz d70fb855dce6c9f1c22598beea11a690 kernel-modules-5.15.38-x86_64-1.txz 77d4774cf78e922637e0313696608d49 kernel-source-5.15.38-noarch-1.txz Installation instructions: +------------------------+ Upgrade the packages as root: # upgradepkg kernel-*.txz If you are using an initrd, you'll need to rebuild it. For a 32-bit SMP machine, use this command (substitute the appropriate kernel version if you are not running Slackware 15.0): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.38-smp | bash For a 64-bit machine, or a 32-bit uniprocessor machine, use this command (substitute the appropriate kernel version if you are not running Slackware 15.0): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.38 | bash Please note that "uniprocessor" has to do with the kernel you are running, not with the CPU. Most systems should run the SMP kernel (if they can) regardless of the number of cores the CPU has. If you aren't sure which kernel you are running, run "uname -a". If you see SMP there, you are running the SMP kernel and should use the 5.15.38-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 5.15.38 as the version. If you are using lilo or elilo to boot the machine, you'll need to ensure that the machine is properly prepared before rebooting. If using LILO: By default, lilo.conf contains an image= line that references a symlink that always points to the correct kernel. No editing should be required unless your machine uses a custom lilo.conf. If that is the case, be sure that the image= line references the correct kernel file. Either way, you'll need to run "lilo" as root to reinstall the boot loader. If using elilo: Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish to use, and then run eliloconfig to update the EFI SystemPartition. +-----+ . Recent updates for the Slackware 15.0 kernel tackle significant security vulnerabilities, enhancing the overall system resilience.. Slackware Security, Kernel Update, Linux Patch, System Integrity. . LinuxSecurity.com Team
May 09, 2022
Slackware
217
security advisorysecurity updatecriticalEnterprise Linux 4 ELSA-2006:0759 Critical Seamonkey Security Update
The following updated rpms for Enterprise Linux 4 have been uploaded to the Unbreakable Linux Network: . Enterprise Linux Security Advisory 2006:0759 https://access.redhat.com/errata/RHSA-2006:0759.html The following updated rpms for Enterprise Linux 4 have been uploaded to the Unbreakable Linux Network: i386: devhelp-0.10-0.6.el4.i386.rpm devhelp-devel-0.10-0.6.el4.i386.rpm seamonkey-1.0.7-0.1.el4.1.i386.rpm seamonkey-chat-1.0.7-0.1.el4.1.i386.rpm seamonkey-devel-1.0.7-0.1.el4.1.i386.rpm seamonkey-dom-inspector-1.0.7-0.1.el4.1.i386.rpm seamonkey-js-debugger-1.0.7-0.1.el4.1.i386.rpm seamonkey-mail-1.0.7-0.1.el4.1.i386.rpm seamonkey-nspr-1.0.7-0.1.el4.1.i386.rpm seamonkey-nspr-devel-1.0.7-0.1.el4.1.i386.rpm seamonkey-nss-1.0.7-0.1.el4.1.i386.rpm seamonkey-nss-devel-1.0.7-0.1.el4.1.i386.rpm x86_64: devhelp-0.10-0.6.el4.x86_64.rpm devhelp-devel-0.10-0.6.el4.x86_64.rpm seamonkey-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-chat-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-devel-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-dom-inspector-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-js-debugger-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-mail-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-nspr-1.0.7-0.1.el4.1.i386.rpm seamonkey-nspr-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-nspr-devel-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-nss-1.0.7-0.1.el4.1.i386.rpm seamonkey-nss-1.0.7-0.1.el4.1.x86_64.rpm seamonkey-nss-devel-1.0.7-0.1.el4.1.x86_64.rpm SRPMS: https://oss.oracle.com:443/el4/SRPMS-updates/devhelp-0.10-0.6.el4.src.rpm https://oss.oracle.com:443/el4/SRPMS-updates/seamonkey-1.0.7-0.1.el4.1.src.rpm Description of changes: [1.0.7-0.1.el4.1] - Replace default bookmarks and prefs [1.0.7-0.1.el4] - Update to 1.0.7 (RC) . Important Oracle ELSA-2007:0847 security patch for Firefox in Enterprise Linux 5 resolves major vulnerabilities.. Enterprise Linux Update, Seamonkey Security, Oracle Security Advisory, Linux Software Patches. . Severity: Critical. LinuxSecurity.com Team
Dec 20, 2006
•Critical
Oracle
100
security advisoryremote code executionmoderate severitySUSE: 2006-008 Moderate: openssh Remote Code Execution Risk
A problem in the handling of scp in openssh could be used to execute A problem in the handling of scp in openssh could be used to execute commands on remote hosts even using a scp-only configuration. commands on remote hosts even using a scp-only configuration. This requires doing a remote-remote scp and a hostile server. (CVE-2006-0225) On SUSE Linux Enterprise Server 9 the xauth pollution prob [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: openssh Announcement ID: SUSE-SA:2006:008 Date: Tue, 14 Feb 2006 11:00:00 +0000 Affected Products: SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote code execution Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-0225 Content of This Advisory: 1) Security Vulnerability Resolved: scp double expansion Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion A problem in the handling of scp in openssh could be used to execute commands on remote hosts even using a scp-only configuration. This requires doing aremote-remote scp and a hostile server. (CVE-2006-0225) On SUSE Linux Enterprise Server 9 the xauth pollution problem was fixed too. The security fix changes the handling of quoting filenames which might break automated scripts using this functionality. Please check that your automated scp scripts still work after the update. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please restart the sshd service after the update. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.0: 3b4e0557d7d0a2b1d23b2c426af95df9 ac11a5ad265e171674485961472baaaf SUSE LINUX 9.3: 2c6d16e14134a1a4f1aaba9ac4aef97f 4cab20c7e83f6de0e440383939e69ec5 SUSE LINUX 9.2: 9b8cf778290ac743fd07445799f79b1f 003115e216c2b36da09ec3679744ba3d SUSE LINUX 9.1: 6e89bdd71e10933bf8e95dc7fad0c289 3d0446f739bcea3715e6945d253b0d53 Power PC Platform: SUSE LINUX 10.0: 3970357da536041d1ae3f7e42655aac7 6a79a95ece5bc7738998adad11205f2f x86-64 Platform: SUSE LINUX 10.0: e9eec927db0859a76851d1b94fa7923d b4a2b9cf969794d1deb1abd07f192786 SUSE LINUX 9.3: 65416ca8578374fa4db63ed9e67f41a3 3fef6bb43541532a654b09dd46201f69 SUSE LINUX 9.2: 3373a79ef05695446f72fdc1a3ec2d44 37ac73c4c9a7723fdcaeb16671b4c6b9 SUSE LINUX 9.1: d04d20e03a63676d5c3349c382318194 ea0deb3eef9970963af2c8c0adce6a7b Sources: SUSE LINUX 10.0: 97ffd38b1144c4797d474c7de1eb6f51 SUSE LINUX 9.3: 1d43324b9d51941bf60e8e0bcbfa25c7 SUSE LINUX 9.2: 647e4b45eba8dd5399c30dcb64db0c91 SUSE LINUX 9.1: cf86431c7c2b1b0b58f6a5f4fff92893 c04ea03236cd9955c5f21f8c15a35416 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: https://www.suse.com:443/ ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE updatepackages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. 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) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal 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, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Feb 14, 2006
•Important
SuSE
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
What got you started with Linux?
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!