A content injection vulnerability was found in the ABRT post-create event handler scripts in libreport. The event script queries the systemd journal for log entries matching the crashed process and writes the results to files in the dump directory without sanitizing embedded control characters. A local user can inject arbitrary content into the journal output by embedding newline characters in syslog messages, controlling the content that root writes to dump directory files.

A symlink following vulnerability was found in the ABRT post-create event handler scripts in /etc/libreport/events.d/abrtevent.conf. Event scripts write output files using shell redirections (e.g., "printf ... > $DUMPDIR/varlogmessages") which use open() with OWRONLY|OCREAT|OTRUNC without the ONOFOLLOW flag. If the target file is replaced with a symlink, the shell process (running as root in the abrthandleeventt SELinux domain, which is effectively unconfined) follows the symlink and writes content to the symlink target. In contrast, ddsavetext (used by SetElement) correctly uses ONOFOLLOW. An attacker who has gained filesystem control of the dump directory can replace output files with symlinks pointing to sensitive system files such as /var/spool/cron/root.

A flaw was found in libinput. An attacker capable of deploying a Lua plugin file in specific system directories can exploit a dangling pointer vulnerability. This occurs when a garbage collection cleanup function is called, leaving a pointer that can then be printed to system logs. This could potentially expose sensitive data if the memory location is re-used, leading to information disclosure. For this exploit to work, Lua plugins must be enabled in libinput and loaded by the compositor.

A flaw was found in libinput. A local attacker who can place a specially crafted Lua bytecode file in certain system or user configuration directories can bypass security restrictions. This allows the attacker to run unauthorized code with the same permissions as the program using libinput, such as a graphical compositor. This could lead to the attacker monitoring keyboard input and sending that information to an external location.

PHP is vulnerable to the Marvin Attack

Chromium: CVE-2024-6293 Use after free in Dawn

Argument Injection in PHP-CGI

Filter bypass in filtervar (FILTERVALIDATEURL)

Command injection via array-ish $command parameter of procopen() (bypass CVE-2024-1874 fix)

Chromium: CVE-2024-5499 Out of bounds write in Streams API

Chromium: CVE-2024-5497 Out of bounds memory access in Keyboard Inputs

Chromium: CVE-2024-5493 Heap buffer overflow in WebRTC

Chromium: CVE-2024-5834 Inappropriate implementation in Dawn

Chromium: CVE-2024-5830 Type Confusion in V8

Chromium: CVE-2024-5833 Type Confusion in V8

Chromium: CVE-2024-5838 Type Confusion in V8

Chromium: CVE-2024-6292 Use after free in Dawn

Chromium: CVE-2024-5837 Type Confusion in V8

Chromium: CVE-2024-6290 Use after free in Dawn

Chromium: CVE-2024-5158 Type Confusion in V8

Chromium: CVE-2024-5835 Heap buffer overflow in Tab Groups

Chromium: CVE-2024-5836 Inappropriate Implementation in DevTools

btrfs: make sure that WRITTEN is set on all metadata blocks

Chromium: CVE-2024-5274 Type Confusion in V8

In the Linux kernel, the following vulnerability has been resolved:

dyndbg: fix old BUGON in >control parser

Fix a BUGON from 2009. Even if it looks "unreachable" (I didn't really look), lets make sure by removing it, doing prerr and return -EINVAL instead.

Chromium: CVE-2024-5847 Use after free in PDFium

Chromium: CVE-2024-5846 Use after free in PDFium

Chromium: CVE-2024-4761 Out of bounds write in V8

Use after free issue in editcap could cause denial of service via crafted capture file

MONGO and ZigBee TLV dissector infinite loops in Wireshark 4.2.0 to 4.2.4, 4.0.0 to 4.0.14, and 3.6.0 to 3.6.22 allow denial of service via packet injection or crafted capture file