Vulnerabilities

The Spiffy Calendar WordPress plugin before 4.9.9 doesn't check the event_author parameter, and allows any user to alter it when creating an event, leading to deceiving users/admins that a page was created by a Contributor+.

The Fatal Error Notify WordPress plugin before 1.5.3 does not have authorisation and CSRF checks in its test_error AJAX action, allowing any authenticated users, such as subscriber to call it and spam the admin email address with error messages. The issue is also exploitable via CSRF

The WP Dashboard Notes WordPress plugin before 1.0.11 is vulnerable to Insecure Direct Object References (IDOR) in post_id= parameter. Authenticated users are able to delete private notes associated with different user accounts. This poses a significant security risk as it violates the principle of least privilege and compromises the integrity and privacy of user data.

The Persian Fonts WordPress plugin through 1.6 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

Malicious code injection in Apache Ambari in prior to 2.7.8. Users are recommended to upgrade to version 2.7.8, which fixes this issue.<br /> <br /> Impact:<br /> A Cluster Operator can manipulate the request by adding a malicious code injection and gain a root over the cluster main host.

Apache James prior to version 3.7.5 and 3.8.0 exposes a JMX endpoint on localhost subject to pre-authentication deserialisation of untrusted data.<br /> Given a deserialisation gadjet, this could be leveraged as part of an exploit chain that could result in privilege escalation.<br /> Note that by default JMX endpoint is only bound locally.<br /> <br /> We recommend users to:<br />  - Upgrade to a non-vulnerable Apache James version<br /> <br />  - Run Apache James isolated from other processes (docker - dedicated virtual machine)<br />  - If possible turn off JMX<br /> <br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nft_limit: avoid possible divide error in nft_limit_init<br /> <br /> div_u64() divides u64 by u32.<br /> <br /> nft_limit_init() wants to divide u64 by u64, use the appropriate<br /> math function (div64_u64)<br /> <br /> divide error: 0000 [#1] PREEMPT SMP KASAN<br /> CPU: 1 PID: 8390 Comm: syz-executor188 Not tainted 5.12.0-rc4-syzkaller #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011<br /> RIP: 0010:div_u64_rem include/linux/math64.h:28 [inline]<br /> RIP: 0010:div_u64 include/linux/math64.h:127 [inline]<br /> RIP: 0010:nft_limit_init+0x2a2/0x5e0 net/netfilter/nft_limit.c:85<br /> Code: ef 4c 01 eb 41 0f 92 c7 48 89 de e8 38 a5 22 fa 4d 85 ff 0f 85 97 02 00 00 e8 ea 9e 22 fa 4c 0f af f3 45 89 ed 31 d2 4c 89 f0 f7 f5 49 89 c6 e8 d3 9e 22 fa 48 8d 7d 48 48 b8 00 00 00 00 00<br /> RSP: 0018:ffffc90009447198 EFLAGS: 00010246<br /> RAX: 0000000000000000 RBX: 0000200000000000 RCX: 0000000000000000<br /> RDX: 0000000000000000 RSI: ffffffff875152e6 RDI: 0000000000000003<br /> RBP: ffff888020f80908 R08: 0000200000000000 R09: 0000000000000000<br /> R10: ffffffff875152d8 R11: 0000000000000000 R12: ffffc90009447270<br /> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000<br /> FS: 000000000097a300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00000000200001c4 CR3: 0000000026a52000 CR4: 00000000001506e0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> nf_tables_newexpr net/netfilter/nf_tables_api.c:2675 [inline]<br /> nft_expr_init+0x145/0x2d0 net/netfilter/nf_tables_api.c:2713<br /> nft_set_elem_expr_alloc+0x27/0x280 net/netfilter/nf_tables_api.c:5160<br /> nf_tables_newset+0x1997/0x3150 net/netfilter/nf_tables_api.c:4321<br /> nfnetlink_rcv_batch+0x85a/0x21b0 net/netfilter/nfnetlink.c:456<br /> nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:580 [inline]<br /> nfnetlink_rcv+0x3af/0x420 net/netfilter/nfnetlink.c:598<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]<br /> netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338<br /> netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927<br /> sock_sendmsg_nosec net/socket.c:654 [inline]<br /> sock_sendmsg+0xcf/0x120 net/socket.c:674<br /> ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350<br /> ___sys_sendmsg+0xf3/0x170 net/socket.c:2404<br /> __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433<br /> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ixgbe: Fix NULL pointer dereference in ethtool loopback test<br /> <br /> The ixgbe driver currently generates a NULL pointer dereference when<br /> performing the ethtool loopback test. This is due to the fact that there<br /> isn&amp;#39;t a q_vector associated with the test ring when it is setup as<br /> interrupts are not normally added to the test rings.<br /> <br /> To address this I have added code that will check for a q_vector before<br /> returning a napi_id value. If a q_vector is not present it will return a<br /> value of 0.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: idxd: fix wq cleanup of WQCFG registers<br /> <br /> A pre-release silicon erratum workaround where wq reset does not clear<br /> WQCFG registers was leaked into upstream code. Use wq reset command<br /> instead of blasting the MMIO region. This also address an issue where<br /> we clobber registers in future devices.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: idxd: clear MSIX permission entry on shutdown<br /> <br /> Add disabling/clearing of MSIX permission entries on device shutdown to<br /> mirror the enabling of the MSIX entries on probe. Current code left the<br /> MSIX enabled and the pasid entries still programmed at device shutdown.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: idxd: fix wq size store permission state<br /> <br /> WQ size can only be changed when the device is disabled. Current code<br /> allows change when device is enabled but wq is disabled. Change the check<br /> to detect device state.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback<br /> <br /> Current code blindly writes over the SWERR and the OVERFLOW bits. Write<br /> back the bits actually read instead so the driver avoids clobbering the<br /> OVERFLOW bit that comes after the register is read.