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 524
Alerts This Week
Warning Icon 1 524

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 9 articles for you...
99

Slackware 15.0: 2025-140-01: glibc critical: local library exploit

New glibc packages are available for Slackware 15.0 to fix a security issue. . -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [slackware-security] glibc (SSA:2025-140-01) New glibc packages are available for Slackware 15.0 to fix a security issue. Here are the details from the Slackware 15.0 ChangeLog: +--------------------------+ patches/packages/aaa_glibc-solibs-2.33-i586-8_slack15.0.txz: Rebuilt. patches/packages/glibc-2.33-i586-8_slack15.0.txz: Rebuilt. This update fixes a security issue: elf: static setuid binary dlopen may incorrectly search LD_LIBRARY_PATH. A statically linked setuid binary that calls dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo) may incorrectly search LD_LIBRARY_PATH to determine which library to load, leading to the execution of library code that is attacker controlled. The only viable vector for exploitation of this bug is local, if a static setuid program exists, and that program calls dlopen, then it may search LD_LIBRARY_PATH to locate the SONAME to load. No such program has been discovered at the time of publishing this advisory, but the presence of custom setuid programs, although strongly discouraged as a security practice, cannot be discounted. For more information, see: https://www.cve.org/CVERecord?id=CVE-2025-4802 (* Security fix *) patches/packages/glibc-i18n-2.33-i586-8_slack15.0.txz: Rebuilt. patches/packages/glibc-profile-2.33-i586-8_slack15.0.txz: Rebuilt. +--------------------------+ Where to find the new packages: +-----------------------------+ Thanks to the friendly folks at the OSU Open Source Lab (http://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 Slackware15.0: ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/aaa_glibc-solibs-2.33-i586-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/glibc-2.33-i586-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/glibc-i18n-2.33-i586-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/glibc-profile-2.33-i586-8_slack15.0.txz Updated packages for Slackware x86_64 15.0: ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/aaa_glibc-solibs-2.33-x86_64-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/glibc-2.33-x86_64-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/glibc-i18n-2.33-x86_64-8_slack15.0.txz ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/glibc-profile-2.33-x86_64-8_slack15.0.txz MD5 signatures: +-------------+ Slackware 15.0 packages: 0d6fe8fe463ebaf50ad2f335635d801d aaa_glibc-solibs-2.33-i586-8_slack15.0.txz 4f5f063a67b275a8eab96ace5cadbc7d glibc-2.33-i586-8_slack15.0.txz 59316f8f6f5ecb043da509b615af8061 glibc-i18n-2.33-i586-8_slack15.0.txz 1afddcd24eee4f113e7562c530b73ec1 glibc-profile-2.33-i586-8_slack15.0.txz Slackware x86_64 15.0 packages: f0c598d8e66dd091365799e0ed018297 aaa_glibc-solibs-2.33-x86_64-8_slack15.0.txz 2e1bf009814661164c9553c15a9ea5f2 glibc-2.33-x86_64-8_slack15.0.txz c71a388da759ac908b619c9ef773c8bf glibc-i18n-2.33-x86_64-8_slack15.0.txz 2b356a71d4e6766e9d4bee16c9ed7ac4 glibc-profile-2.33-x86_64-8_slack15.0.txz Installation instructions: +------------------------+ Upgrade the packages as root: # upgradepkg *glibc-*.txz +-----+ . Updated glibc packages have been released for Slackware 15.0 to address a vulnerability associated with dynamic library loading.. glibc package security, Slackware update, local exploit risk. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 May 20, 2025 Critical Slackware
172

Ubuntu 16.04 LTS: USN-4007-2 Critical: Linux Kernel ASLR Bypass

A system hardening measure could be bypassed.. =========================================================================Ubuntu Security Notice USN-4007-2 June 04, 2019 linux-aws-hwe, linux-hwe, linux-oracle vulnerability ========================================================================= A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 16.04 LTS Summary: A system hardening measure could be bypassed. Software Description: - linux-aws-hwe: Linux kernel for Amazon Web Services (AWS-HWE) systems - linux-hwe: Linux hardware enablement (HWE) kernel - linux-oracle: Linux kernel for Oracle Cloud systems Details: USN-4007-1 fixed vulnerabilities in the Linux kernel for Ubuntu 18.04 LTS. This update provides the corresponding updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 18.04 LTS for Ubuntu 16.04 LTS. Federico Manuel Bento discovered that the Linux kernel did not properly apply Address Space Layout Randomization (ASLR) in some situations for setuid a.out binaries. A local attacker could use this to improve the chances of exploiting an existing vulnerability in a setuid a.out binary. As a hardening measure, this update disables a.out support. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 16.04 LTS: linux-image-4.15.0-1014-oracle 4.15.0-1014.16~16.04.1 linux-image-4.15.0-1040-aws 4.15.0-1040.42~16.04.1 linux-image-4.15.0-51-generic 4.15.0-51.55~16.04.1 linux-image-4.15.0-51-generic-lpae 4.15.0-51.55~16.04.1 linux-image-4.15.0-51-lowlatency 4.15.0-51.55~16.04.1 linux-image-aws-hwe 4.15.0.1040.40 linux-image-generic-hwe-16.04 4.15.0.51.72 linux-image-generic-lpae-hwe-16.04 4.15.0.51.72 linux-image-lowlatency-hwe-16.04 4.15.0.51.72 linux-image-oem 4.15.0.51.72 linux-image-oracle 4.15.0.1014.8 linux-image-virtual-hwe-16.04 4.15.0.51.72 After a standard system update you need to reboot your computer tomake all the necessary changes. ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well. References: https://ubuntu.com/security/notices/USN-4007-2 https://ubuntu.com/security/notices/USN-4007-1 CVE-2019-11191 Package Information: https://launchpad.net/ubuntu/+source/linux-aws-hwe/4.15.0-1040.42~16.04.1 https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-51.55~16.04.1 https://launchpad.net/ubuntu/+source/linux-oracle/4.15.0-1014.16~16.04.1 . Ubuntu 16.04 LTS advisory covering kernel hardening and necessary updates for critical security issues.. Ubuntu Kernel Updates, Linux HWE Security, ASLR Bypass, System Hardening. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jun 04, 2019 Critical Ubuntu
172

Ubuntu 18.04 LTS: USN-4007-1 Critical: Kernel ASLR Bypass

A system hardening measure could be bypassed.. =========================================================================Ubuntu Security Notice USN-4007-1 June 04, 2019 linux, linux-aws, linux-gcp, linux-kvm, linux-oem, linux-oracle, linux-raspi2, linux-snapdragon vulnerability ========================================================================= A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 18.04 LTS Summary: A system hardening measure could be bypassed. Software Description: - linux: Linux kernel - linux-aws: Linux kernel for Amazon Web Services (AWS) systems - linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems - linux-kvm: Linux kernel for cloud environments - linux-meta: - linux-oem: Linux kernel for OEM processors - linux-oracle: Linux kernel for Oracle Cloud systems - linux-raspi2: Linux kernel for Raspberry Pi 2 - linux-snapdragon: Linux kernel for Snapdragon processors Details: Federico Manuel Bento discovered that the Linux kernel did not properly apply Address Space Layout Randomization (ASLR) in some situations for setuid a.out binaries. A local attacker could use this to improve the chances of exploiting an existing vulnerability in a setuid a.out binary. As a hardening measure, this update disables a.out support. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 18.04 LTS: linux-image-4.15.0-1014-oracle 4.15.0-1014.16 linux-image-4.15.0-1033-gcp 4.15.0-1033.35 linux-image-4.15.0-1035-kvm 4.15.0-1035.35 linux-image-4.15.0-1037-raspi2 4.15.0-1037.39 linux-image-4.15.0-1039-oem 4.15.0-1039.44 linux-image-4.15.0-1040-aws 4.15.0-1040.42 linux-image-4.15.0-1054-snapdragon 4.15.0-1054.58 linux-image-4.15.0-51-generic 4.15.0-51.55 linux-image-4.15.0-51-generic-lpae 4.15.0-51.55 linux-image-4.15.0-51-lowlatency 4.15.0-51.55 linux-image-aws 4.15.0.1040.39 linux-image-gcp 4.15.0.1033.35 linux-image-generic 4.15.0.51.53 linux-image-generic-lpae 4.15.0.51.53 linux-image-kvm 4.15.0.1035.35 linux-image-lowlatency 4.15.0.51.53 linux-image-oem 4.15.0.1039.43 linux-image-oracle 4.15.0.1014.17 linux-image-raspi2 4.15.0.1037.35 linux-image-snapdragon 4.15.0.1054.57 After a standard system update you need to reboot your computer to make all the necessary changes. ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well. References: https://ubuntu.com/security/notices/USN-4007-1 CVE-2019-11191 Package Information: https://launchpad.net/ubuntu/+source/linux/4.15.0-51.55 https://launchpad.net/ubuntu/+source/linux-aws/4.15.0-1040.42 https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1033.35 https://launchpad.net/ubuntu/+source/linux-kvm/4.15.0-1035.35 https://launchpad.net/ubuntu/+source/linux-meta/4.15.0.51.53 https://launchpad.net/ubuntu/+source/linux-oem/4.15.0-1039.44 https://launchpad.net/ubuntu/+source/linux-oracle/4.15.0-1014.16 https://launchpad.net/ubuntu/+source/linux-raspi2/4.15.0-1037.39 https://launchpad.net/ubuntu/+source/linux-snapdragon/4.15.0-1054.58 . Critical security notice for Ubuntu regarding a circumvention of kernel protection protocols impacting various deployments.. Ubuntu Security, Linux Kernel Issues, System Hardening, ASLR Bypass, Setuid Exploit. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jun 04, 2019 Critical Ubuntu
172

Ubuntu 16.04 LTS: USN-4008-1 Critical: Linux Kernel Denial Of Service

Several security issues were fixed in the Linux kernel.. =========================================================================Ubuntu Security Notice USN-4008-1 June 04, 2019 linux, linux-aws, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities ========================================================================= A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 16.04 LTS Summary: Several security issues were fixed in the Linux kernel. Software Description: - linux: Linux kernel - linux-aws: Linux kernel for Amazon Web Services (AWS) systems - linux-kvm: Linux kernel for cloud environments - linux-raspi2: Linux kernel for Raspberry Pi 2 - linux-snapdragon: Linux kernel for Snapdragon processors Details: Robert Święcki discovered that the Linux kernel did not properly apply Address Space Layout Randomization (ASLR) in some situations for setuid elf binaries. A local attacker could use this to improve the chances of exploiting an existing vulnerability in a setuid elf binary. (CVE-2019-11190) It was discovered that a null pointer dereference vulnerability existed in the LSI Logic MegaRAID driver in the Linux kernel. A local attacker could use this to cause a denial of service (system crash). (CVE-2019-11810) It was discovered that a race condition leading to a use-after-free existed in the Reliable Datagram Sockets (RDS) protocol implementation in the Linux kernel. The RDS protocol is blacklisted by default in Ubuntu. If enabled, a local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2019-11815) Federico Manuel Bento discovered that the Linux kernel did not properly apply Address Space Layout Randomization (ASLR) in some situations for setuid a.out binaries. A local attacker could use this to improve the chances of exploiting an existing vulnerability in a setuid a.out binary. (CVE-2019-11191) As a hardening measure, this update disables a.outsupport. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 16.04 LTS: linux-image-4.4.0-1047-kvm 4.4.0-1047.53 linux-image-4.4.0-1084-aws 4.4.0-1084.94 linux-image-4.4.0-1110-raspi2 4.4.0-1110.118 linux-image-4.4.0-1114-snapdragon 4.4.0-1114.119 linux-image-4.4.0-150-generic 4.4.0-150.176 linux-image-4.4.0-150-generic-lpae 4.4.0-150.176 linux-image-4.4.0-150-lowlatency 4.4.0-150.176 linux-image-4.4.0-150-powerpc-e500mc 4.4.0-150.176 linux-image-4.4.0-150-powerpc-smp 4.4.0-150.176 linux-image-4.4.0-150-powerpc64-emb 4.4.0-150.176 linux-image-4.4.0-150-powerpc64-smp 4.4.0-150.176 linux-image-aws 4.4.0.1084.87 linux-image-generic 4.4.0.150.158 linux-image-generic-lpae 4.4.0.150.158 linux-image-kvm 4.4.0.1047.47 linux-image-lowlatency 4.4.0.150.158 linux-image-powerpc-e500mc 4.4.0.150.158 linux-image-powerpc-smp 4.4.0.150.158 linux-image-powerpc64-emb 4.4.0.150.158 linux-image-powerpc64-smp 4.4.0.150.158 linux-image-raspi2 4.4.0.1110.110 linux-image-snapdragon 4.4.0.1114.106 linux-image-virtual 4.4.0.150.158 After a standard system update you need to reboot your computer to make all the necessary changes. ATTENTION: Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well. References: https://ubuntu.com/security/notices/USN-4008-1 CVE-2019-11190, CVE-2019-11191, CVE-2019-11810, CVE-2019-11815 Package Information: https://launchpad.net/ubuntu/+source/linux/4.4.0-150.176 https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1084.94 https://launchpad.net/ubuntu/+source/linux-kvm/4.4.0-1047.53 https://launchpad.net/ubuntu/+source/linux-raspi2/4.4.0-1110.118 https://launchpad.net/ubuntu/+source/linux-snapdragon/4.4.0-1114.119 . An essential alert addressing several security flaws found in the Ubuntu kernel, alongside suggested steps for resolution.. Ubuntu Kernel Issues, Linux Security Updates, DoS Threats, Setuid Exploitation, ASLR Misconfigurations. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jun 04, 2019 Critical Ubuntu
202

openSUSE: 2019:1227-1 Important: lxc and lxcfs Security Issues

An update that solves two vulnerabilities and has one errata is now available.. openSUSE Security Update: Security update for lxc, lxcfs ______________________________________________________________________________ Announcement ID: openSUSE-SU-2019:1227-1 Rating: important References: #1122185 #1131762 #988348 Cross-References: CVE-2018-6556 CVE-2019-5736 Affected Products: openSUSE Backports SLE-15 ______________________________________________________________________________ An update that solves two vulnerabilities and has one errata is now available. Description: This update for lxc, lxcfs to version 3.1.0 fixes the following issues: Security issues fixed: - CVE-2019-5736: Fixed a container breakout vulnerability (boo#1122185). - CVE-2018-6556: Enable setuid bit on lxc-user-nic (boo#988348). Non-security issues fixed: - Update to LXC 3.1.0. The changelog is far too long to include here, please look at https://linuxcontainers.org/. (boo#1131762) Patch Instructions: To install this openSUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: - openSUSE Backports SLE-15: zypper in -t patch openSUSE-2019-1227=1 Package List: - openSUSE Backports SLE-15 (aarch64 ppc64le s390x x86_64): liblxc-devel-3.1.0-bp150.5.3.1 liblxc1-3.1.0-bp150.5.3.1 lxc-3.1.0-bp150.5.3.1 lxcfs-3.0.3-bp150.3.3.1 lxcfs-debuginfo-3.0.3-bp150.3.3.1 lxcfs-debugsource-3.0.3-bp150.3.3.1 pam_cgfs-3.1.0-bp150.5.3.1 - openSUSE Backports SLE-15 (noarch): lxc-bash-completion-3.1.0-bp150.5.3.1 lxcfs-hooks-lxc-3.0.3-bp150.3.3.1 References: https://www.suse.com/security/cve/CVE-2018-6556.html https://www.suse.com/security/cve/CVE-2019-5736.html https://bugzilla.suse.com/1122185 https://bugzilla.suse.com/1131762 https://bugzilla.suse.com/988348 -- . Vital openSUSE patch tackles lxc and lxcfs vulnerabilities, implementing essential corrections and improvements for bolstered security measures.. openSUSE Update, lxc Security Fix, lxcfs Update, Container Security, lxc Vulnerability. . Severity: Important. LinuxSecurity.com Team

Calendar%202 Apr 17, 2019 Important OpenSUSE
89

Fedora 27: FEDORA-2018-9b7d7a155b Moderate: Flatpak Setuid Risk

flatpak 1.0.6 release. This release fixes an issue that lets system-wide installed applications create setuid root files inside their app dir (somewhere in /var/lib/flatpak/app). Setuid support is disabled inside flatpaks, so such files are only a risk if the user runs them manually outside flatpak. Installing a flatpak system-wide is needs root access, so this isn't a privilege. --------------------------------------------------------------------------------Fedora Update Notification FEDORA-2018-9b7d7a155b 2018-11-27 03:12:43.615116 --------------------------------------------------------------------------------Name : flatpak Product : Fedora 27 Version : 1.0.6 Release : 1.fc27 URL : https://flatpak.org/ Summary : Application deployment framework for desktop apps Description : flatpak is a system for building, distributing and running sandboxed desktop applications on Linux. See https://wiki.gnome.org/Projects/SandboxedApps for more information. --------------------------------------------------------------------------------Update Information: flatpak 1.0.6 release. This release fixes an issue that lets system-wide installed applications create setuid root files inside their app dir (somewhere in /var/lib/flatpak/app). Setuid support is disabled inside flatpaks, so such files are only a risk if the user runs them manually outside flatpak. Installing a flatpak system-wide is needs root access, so this isn't a privilege elevation for non-root users, and allowing root to install setuid files is something all traditional packaging systems allow. However flatpak tries to be better than that, in order to make it easier to trust third party repositories. Changes in this version: * The permissions of the files created by the apply_extra script is canonicalized and the script itself is run without any capabilities. * Better matching of existing remotes when the local and remote configuration differs wrt collection ids. * Newflatpakrepo DeployCollectionID replaces CollectionID, doing the same thing. It is recommended to use this instead because older versions of flatpak has bugs in the support of collection ids, and this key will only be respected in versions where it works. * The X11 socket is now mounted read-only. ----flatpak 1.0.5 release. There was a sandbox bug in the previous version where parts of the runtime /etc was not mounted read-only. In case the runtime was installed as the user (not the default) this means that the app could modify files on the runtime. Nothing in the host uses the runtime files, so this is not a direct sandbox escape, but it is possible that an app can confuse a different app that has higher permissions and so gain privileges. Detailed changes: * Make the /etc -> /usr/etc bind-mounts read-only. * Make various app-specific configuration files read-only. * flatpak is more picky about remote names to avoid problems with storing weird names in the ostree config. * A segfault in libflatpak handling of bundles was fixed. * Updated translations * Fixed a regression in flatpak run that caused problems running user-installed apps when the system installation was broken. In addition to upstream changes, this update also fixes a packaging issue and adds a missing dependency on p11-kit-server to fix accessing host TLS certificates. --------------------------------------------------------------------------------ChangeLog: * Fri Nov 16 2018 Kalev Lember - 1.0.6-1 - Update to 1.0.6 * Mon Nov 12 2018 Kalev Lember - 1.0.5-2 - Recommend p11-kit-server instead of just p11-kit (#1649049) * Mon Nov 12 2018 Kalev Lember - 1.0.5-1 - Update to 1.0.5 * Fri Oct 12 2018 Kalev Lember - 1.0.4-1 - Update to 1.0.4 * Thu Oct 4 2018 Kalev Lember - 1.0.3-1 - Update to 1.0.3 * Thu Sep 13 2018 Kalev Lember - 1.0.2-1 - Update to 1.0.2 * Tue Aug 28 2018 David King - 1.0.1-1 - Update to 1.0.1 * Mon Aug 20 2018 David King - 1.0.0-1 - Update to 1.0.0 * Tue Jul 102018 Kalev Lember - 0.99.3-1 - Update to 0.99.3 * Wed Jun 27 2018 Kalev Lember - 0.99.2-1 - Update to 0.99.2 * Thu Jun 21 2018 David King - 0.99.1-1 - Update to 0.99.1 * Thu Mar 22 2018 Kalev Lember - 0.10.4-1 - Update to 0.10.4 * Tue Jan 30 2018 Kalev Lember - 0.10.3-1 - Update to 0.10.3 * Thu Dec 21 2017 David King - 0.10.2.1-1 - Update to 0.10.2.1 * Fri Dec 15 2017 Kalev Lember - 0.10.2-1 - Update to 0.10.2 * Fri Nov 24 2017 David King - 0.10.1-1 - Update to 0.10.1 * Thu Oct 26 2017 Kalev Lember - 0.10.0-1 - Update to 0.10.0 --------------------------------------------------------------------------------References: [ 1 ] Bug #1649049 - missing dependency on p11-kit-server https://bugzilla.redhat.com/show_bug.cgi?id=1649049 --------------------------------------------------------------------------------This update can be installed with the "dnf" update program. Use su -c 'dnf upgrade --advisory FEDORA-2018-9b7d7a155b' at the command line. For more information, refer to the dnf documentation available at https://dnf.readthedocs.io/en/latest/command_ref.html 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/security/ --------------------------------------------------------------------------------_______________________________________________ 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./ . Flatpak 1.0.6 update boosts security, addressing vulnerabilities related to setuid root files and permission settings in Fedora 27.. Fedora Flatpak Security Update, ApplicationDeployment, System-Wide Issues, Privilege Protection. . LinuxSecurity.com Team

Calendar%202 Nov 27, 2018 Fedora
172

Ubuntu 12.04 ESM USN-3323-2 Critical: eglibc Memory Exploit

Gnu C library could be made to run programs as an administrator.. =========================================================================Ubuntu Security Notice USN-3323-2 June 29, 2017 eglibc vulnerability ========================================================================= A security issue affects these releases of Ubuntu and its derivatives: - Ubuntu 12.04 ESM Summary: Gnu C library could be made to run programs as an administrator. Software Description: - eglibc: GNU C Library Details: USN-3323-1 fixed a vulnerability in the GNU C Library. This update provides the corresponding update for Ubuntu 12.04 ESM. Original advisory details: It was discovered that the GNU C library did not properly handle memory when processing environment variables for setuid programs. A local attacker could use this in combination with another vulnerability to gain administrative privileges. Update instructions: The problem can be corrected by updating your system to the following package versions: Ubuntu 12.04 ESM: libc6 2.15-0ubuntu10.20 After a standard system update you need to reboot your computer to make all the necessary changes. References: https://ubuntu.com/security/notices/USN-3323-2 https://ubuntu.com/security/notices/USN-3323-1 CVE-2017-1000366 . A crucial update to the GNU C Library for Ubuntu 12.04 ESM addresses a major vulnerability related to admin access. Keep your system secure by updating!. GNU C Library Update, eglibc Issue, Ubuntu Security Notice. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jun 29, 2017 Critical Ubuntu
200

Scientific Linux 6.x Important: Glibc Update For Escalation Issue

Important: glibc security and bug fix update. Date: Thu, 3 Mar 2011 15:20:24 -0600 Reply-To: Troy Dawson Sender: Security Errata for Scientific Linux From: Troy Dawson Subject: Security ERRATA Important: glibc on SL6.x i386/x86_64 Comments: To: "This email address is being protected from spambots. You need JavaScript enabled to view it." Synopsis: Important: glibc security and bug fix update Issue date: 2010-11-10 CVE Names: CVE-2010-3847 CVE-2010-3856 It was discovered that the glibc dynamic linker/loader did not handle the $ORIGIN dynamic string token set in the LD_AUDIT environment variable securely. A local attacker with write access to a file system containing setuid or setgid binaries could use this flaw to escalate their privileges. (CVE-2010-3847) It was discovered that the glibc dynamic linker/loader did not perform sufficient safety checks when loading dynamic shared objects (DSOs) to provide callbacks for its auditing API during the execution of privileged programs. A local attacker could use this flaw to escalate their privileges via a carefully-chosen system DSO library containing unsafe constructors. (CVE-2010-3856) This update also fixes the following bugs: * Previously, the generic implementation of the strstr() and memmem() functions did not handle certain periodic patterns correctly and could find a false positive match. This error has been fixed, and both functions now work as expected. (BZ#643341) * The "TCB_ALIGNMENT" value has been increased to 32 bytes to prevent applications from crashing during symbol resolution on 64-bit systems with support for Intel AVX vector registers. (BZ#643343) SL 6.x SRPMS: glibc-2.12-1.7.el6_0.3.src.rpm i386: glibc-2.12-1.7.el6_0.3.i686.rpm glibc-common-2.12-1.7.el6_0.3.i686.rpm glibc-devel-2.12-1.7.el6_0.3.i686.rpm glibc-headers-2.12-1.7.el6_0.3.i686.rpm glibc-static-2.12-1.7.el6_0.3.i686.rpm glibc-utils-2.12-1.7.el6_0.3.i686.rpm nscd-2.12-1.7.el6_0.3.i686.rpm x86_64: glibc-2.12-1.7.el6_0.3.i686.rpm glibc-2.12-1.7.el6_0.3.x86_64.rpm glibc-common-2.12-1.7.el6_0.3.x86_64.rpm glibc-devel-2.12-1.7.el6_0.3.i686.rpm glibc-devel-2.12-1.7.el6_0.3.x86_64.rpm glibc-headers-2.12-1.7.el6_0.3.x86_64.rpm glibc-static-2.12-1.7.el6_0.3.i686.rpm glibc-static-2.12-1.7.el6_0.3.x86_64.rpm glibc-utils-2.12-1.7.el6_0.3.x86_64.rpm nscd-2.12-1.7.el6_0.3.x86_64.rpm -Connie Sieh -Troy Dawson . Glibc patch rollout tackles privilege elevation vulnerability in Scientific Linux 6.x, featuring important fixes and improvements.. Glibc Security Update, Local Escalation Threat, Scientific Linux Errata. . Severity: Important. LinuxSecurity.com Team

Calendar%202 Mar 03, 2011 Important Scientific Linux
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