Vulnerabilities

The SVG Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REST API SVG File uploads in all versions up to, and including, 1.1.24 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

The MP3 Audio Player – Music Player, Podcast Player & Radio by Sonaar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's sonaar_audioplayer shortcode in all versions up to, and including, 5.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

In the process of testing the MailPoet WordPress plugin before 5.3.2, a vulnerability was found that allows you to implement Stored XSS on behalf of the editor by embedding malicious script, which entails account takeover backdoor

Improper Validation of Specified Type of Input vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5-ENET versions 1.100 to 1.200 and FX5-ENET/IP versions 1.100 to 1.104 allows a remote attacker to cause a Denial of Service condition in Ethernet communication of the products by sending specially crafted SLMP packets.

Versions of the package @eslint/plugin-kit before 0.2.3 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by exploiting this vulnerability.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> regulator: rtq2208: Fix uninitialized use of regulator_config<br /> <br /> Fix rtq2208 driver uninitialized use to cause kernel error.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> HID: core: zero-initialize the report buffer<br /> <br /> Since the report buffer is used by all kinds of drivers in various ways, let&amp;#39;s<br /> zero-initialize it during allocation to make sure that it can&amp;#39;t be ever used<br /> to leak kernel memory via specially-crafted report.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> sctp: properly validate chunk size in sctp_sf_ootb()<br /> <br /> A size validation fix similar to that in Commit 50619dbf8db7 ("sctp: add<br /> size validation when walking chunks") is also required in sctp_sf_ootb()<br /> to address a crash reported by syzbot:<br /> <br /> BUG: KMSAN: uninit-value in sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712<br /> sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712<br /> sctp_do_sm+0x181/0x93d0 net/sctp/sm_sideeffect.c:1166<br /> sctp_endpoint_bh_rcv+0xc38/0xf90 net/sctp/endpointola.c:407<br /> sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88<br /> sctp_rcv+0x3831/0x3b20 net/sctp/input.c:243<br /> sctp4_rcv+0x42/0x50 net/sctp/protocol.c:1159<br /> ip_protocol_deliver_rcu+0xb51/0x13d0 net/ipv4/ip_input.c:205<br /> ip_local_deliver_finish+0x336/0x500 net/ipv4/ip_input.c:233

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> security/keys: fix slab-out-of-bounds in key_task_permission<br /> <br /> KASAN reports an out of bounds read:<br /> BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36<br /> BUG: KASAN: slab-out-of-bounds in uid_eq include/linux/uidgid.h:63 [inline]<br /> BUG: KASAN: slab-out-of-bounds in key_task_permission+0x394/0x410<br /> security/keys/permission.c:54<br /> Read of size 4 at addr ffff88813c3ab618 by task stress-ng/4362<br /> <br /> CPU: 2 PID: 4362 Comm: stress-ng Not tainted 5.10.0-14930-gafbffd6c3ede #15<br /> Call Trace:<br /> __dump_stack lib/dump_stack.c:82 [inline]<br /> dump_stack+0x107/0x167 lib/dump_stack.c:123<br /> print_address_description.constprop.0+0x19/0x170 mm/kasan/report.c:400<br /> __kasan_report.cold+0x6c/0x84 mm/kasan/report.c:560<br /> kasan_report+0x3a/0x50 mm/kasan/report.c:585<br /> __kuid_val include/linux/uidgid.h:36 [inline]<br /> uid_eq include/linux/uidgid.h:63 [inline]<br /> key_task_permission+0x394/0x410 security/keys/permission.c:54<br /> search_nested_keyrings+0x90e/0xe90 security/keys/keyring.c:793<br /> <br /> This issue was also reported by syzbot.<br /> <br /> It can be reproduced by following these steps(more details [1]):<br /> 1. Obtain more than 32 inputs that have similar hashes, which ends with the<br /> pattern &amp;#39;0xxxxxxxe6&amp;#39;.<br /> 2. Reboot and add the keys obtained in step 1.<br /> <br /> The reproducer demonstrates how this issue happened:<br /> 1. In the search_nested_keyrings function, when it iterates through the<br /> slots in a node(below tag ascend_to_node), if the slot pointer is meta<br /> and node-&gt;back_pointer != NULL(it means a root), it will proceed to<br /> descend_to_node. However, there is an exception. If node is the root,<br /> and one of the slots points to a shortcut, it will be treated as a<br /> keyring.<br /> 2. Whether the ptr is keyring decided by keyring_ptr_is_keyring function.<br /> However, KEYRING_PTR_SUBTYPE is 0x2UL, the same as<br /> ASSOC_ARRAY_PTR_SUBTYPE_MASK.<br /> 3. When 32 keys with the similar hashes are added to the tree, the ROOT<br /> has keys with hashes that are not similar (e.g. slot 0) and it splits<br /> NODE A without using a shortcut. When NODE A is filled with keys that<br /> all hashes are xxe6, the keys are similar, NODE A will split with a<br /> shortcut. Finally, it forms the tree as shown below, where slot 6 points<br /> to a shortcut.<br /> <br /> NODE A<br /> +------&gt;+---+<br /> ROOT | | 0 | xxe6<br /> +---+ | +---+<br /> xxxx | 0 | shortcut : : xxe6<br /> +---+ | +---+<br /> xxe6 : : | | | xxe6<br /> +---+ | +---+<br /> | 6 |---+ : : xxe6<br /> +---+ +---+<br /> xxe6 : : | f | xxe6<br /> +---+ +---+<br /> xxe6 | f |<br /> +---+<br /> <br /> 4. As mentioned above, If a slot(slot 6) of the root points to a shortcut,<br /> it may be mistakenly transferred to a key*, leading to a read<br /> out-of-bounds read.<br /> <br /> To fix this issue, one should jump to descend_to_node if the ptr is a<br /> shortcut, regardless of whether the node is root or not.<br /> <br /> [1] https://lore.kernel.org/linux-kernel/1cfa878e-8c7b-4570-8606-21daf5e13ce7@huaweicloud.com/<br /> <br /> [jarkko: tweaked the commit message a bit to have an appropriate closes<br /> tag.]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: vivid: fix buffer overwrite when using &gt; 32 buffers<br /> <br /> The maximum number of buffers that can be requested was increased to<br /> 64 for the video capture queue. But video capture used a must_blank<br /> array that was still sized for 32 (VIDEO_MAX_FRAME). This caused an<br /> out-of-bounds write when using buffer indices &gt;= 32.<br /> <br /> Create a new define MAX_VID_CAP_BUFFERS that is used to access the<br /> must_blank array and set max_num_buffers for the video capture queue.<br /> <br /> This solves a crash reported by:<br /> <br /> https://bugzilla.kernel.org/show_bug.cgi?id=219258

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: av7110: fix a spectre vulnerability<br /> <br /> As warned by smatch:<br /> drivers/staging/media/av7110/av7110_ca.c:270 dvb_ca_ioctl() warn: potential spectre issue &amp;#39;av7110-&gt;ci_slot&amp;#39; [w] (local cap)<br /> <br /> There is a spectre-related vulnerability at the code. Fix it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: dvb-core: add missing buffer index check<br /> <br /> dvb_vb2_expbuf() didn&amp;#39;t check if the given buffer index was<br /> for a valid buffer. Add this check.