SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The implementation of PEAP in wpa_supplicant through 2.10 allows authentication bypass.
For a successful attack, wpa_supplicant must be configured to not verify the network's
TLS certificate during Phase 1 authentication, and an eap_peap_decrypt vulnerability can
then be abused to skip Phase 2 authentication. The attack vector is sending an EAP-TLV
Success packet instead of starting Phase 2. This allows an adversary to impersonate
Enterprise Wi-Fi networks.
Heap Buffer Overflow vulnerability in qpdf 11.9.0 allows attackers to crash
the application via the std::__shared_count() function at /bits/shared_ptr_base.h.
Heap Buffer Overflow vulnerability in qpdf 11.9.0 allows attackers to crash
the application via the std::__shared_count() function at /bits/shared_ptr_base.h.
A flaw was found in the grub2-set-bootflag utility of grub2. After the fix of CVE-2019-14865,
grub2-set-bootflag will create a temporary file with the new grubenv content and rename it to
the original grubenv file. If the program is killed before the rename operation, the temporary
file will not be removed and may fill the filesystem when invoked multiple times, resulting in
a filesystem out of free inodes or blocks.
A flaw was found in the grub2-set-bootflag utility of grub2. After the fix of CVE-2019-14865,
grub2-set-bootflag will create a temporary file with the new grubenv content and rename it to
the original grubenv file. If the program is killed before the rename operation, the temporary
file will not be removed and may fill the filesystem when invoked multiple times, resulting in
a filesystem out of free inodes or blocks.
The util-linux wall command does not filter escape sequences from command line arguments.
The vulnerable code was introduced in commit cdd3cc7fa4 (2013).
Every version since has been vulnerable.
A full report can be found here. I have nicknamed this bug "WallEscape".
The util-linux wall command does not filter escape sequences from command line arguments.
The vulnerable code was introduced in commit cdd3cc7fa4 (2013).
Every version since has been vulnerable.
A full report can be found here. I have nicknamed this bug "WallEscape".
Assigner: Red Hat, Inc.
Published: 2024-03-29Updated: 2024-03-29
Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0. The tarballs included extra .m4 files, which contained instructions for building with automake that did not exist in the repository. These instructions, through a series of complex obfuscations, extract a prebuilt object file from one of the test archives, which is then used to modify specific functions in the code while building the liblzma package. This issue results in liblzma being used by additional software, like sshd, to provide functionality that will be interpreted by the modified functions.
The urgent Red Hat warning can be found via the Red Hat blog.
Debian has also released a similar security message over the malicious code within XZ utils.
Long story short, make sure you don't have XZ 5.6.0/5.6.1 on your systems now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
