GFI MailEssentials versions prior to 21.8 contain a deserialization vulnerability in their .NET implementation. This flaw allows a remote authenticated attacker to execute arbitrary code by sending crafted serialized .NET data when joining a Multi-Server setup. The vulnerability is rated high severity with a CVSS score of 8.8.
A concurrency issue in the Linux kernel's mvpp2 network driver could cause parser TCAM memory corruption. This occurs due to unprotected concurrent modifications of TCAM/SRAM tables and their cached shadow SRAM, leading to potential data corruption and packet drops. The flaw was observed when mvpp2_set_rx_mode() executed simultaneously on two CPUs, corrupting an entry and causing the classifier to drop all incoming unicast packets.
CVE-2019-9875 is a deserialization vulnerability in Sitecore CMS and Experience Platform (XP) within the Sitecore.Security.AntiCSRF module. It allows an authenticated attacker to execute arbitrary code by sending a malicious serialized .NET object in the HTTP POST parameter __CSRFTOKEN. This vulnerability has been exploited in the wild and is considered high severity.
In the Linux kernel, the following vulnerability has been resolved: ax25: Fix refcount leak caused by setting SO_BINDTODEVICE sockopt If an AX25 device is bound to a socket by setting the SO_BINDTODEVICE socket option, a refcount leak will occur in ax25_release(). Commit 9fd75b66b8f6 ("ax25: Fix refcount leaks caused by ax25_cb_del()") added decrement of device refcounts in ax25_release(). In order for that to work correctly the refcounts must already be incremented when the device is bound to the socket. An AX25 device can be bound to a socket by either calling ax25_bind() or setting SO_BINDTODEVICE socket option. In both cases the refcounts should be incremented, but in fact it is done only in ax25_bind(). This bug leads to the following issue reported by Syzkaller: ================================================================ refcount_t: decrement hit 0; leaking memory. WARNING: CPU: 1 PID: 5932 at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210 lib/refcount.c:31 Modules linked in: CPU: 1 UID: 0 PID: 5932 Comm: syz-executor424 Not tainted 6.13.0-rc4-syzkaller-00110-g4099a71718b0 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:refcount_warn_saturate+0x1ed/0x210 lib/refcount.c:31 Call Trace: <TASK> __refcount_dec include/linux/refcount.h:336 [inline] refcount_dec include/linux/refcount.h:351 [inline] ref_tracker_free+0x710/0x820 lib/ref_tracker.c:236 netdev_tracker_free include/linux/netdevice.h:4156 [inline] netdev_put include/linux/netdevice.h:4173 [inline] netdev_put include/linux/netdevice.h:4169 [inline] ax25_release+0x33f/0xa10 net/ax25/af_ax25.c:1069 __sock_release+0xb0/0x270 net/socket.c:640 sock_close+0x1c/0x30 net/socket.c:1408 ... do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... </TASK> ================================================================ Fix the implementation of ax25_setsockopt() by adding increment of refcounts for the new device bound, and decrement of refcounts for the old unbound device.
Gatekeeper v3.15.3 introduces security fixes addressing vulnerabilities in dependencies golang.org/x/crypto/ssh (CVE-2024-45337) and golang.org/x/net/html (CVE-2024-45338). The update allows specifying containerArguments for audit and webhook configurations with restrictions and exempts certain namespaces from admission control by default. The vulnerabilities fixed include an authorization bypass risk and a parsing issue.
Microsoft .NET Framework has an information disclosure vulnerability identified as CVE-2024-29059. This flaw exposes the ObjRef URI to attackers, which can lead to remote code execution. The vulnerability has a high severity score of 7.5 and is known to be exploited in the wild. No specific affected versions or patch information are provided in the available data.
The brodos.net Onlineshop Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'BrodosCategory' shortcode in all versions up to, and including, 2.0.2 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.
.NET 8.0 on Red Hat Enterprise Linux 9.4 has multiple security vulnerabilities including elevation of privilege and remote code execution issues. Updated versions .NET SDK 8.0.112 and .NET Runtime 8.0.12 address these vulnerabilities. The update is rated as Important by Red Hat Product Security.
.NET 8.0 on Red Hat Enterprise Linux has multiple security vulnerabilities including elevation of privilege and remote code execution issues. Updated versions .NET SDK 8.0.112 and .NET Runtime 8.0.1.12 address these vulnerabilities. The update is rated as Important by Red Hat Product Security.
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Remove the direct link to net_device The similar patch in siw is in the link: https://git.kernel.org/rdma/rdma/c/16b87037b48889 This problem also occurred in RXE. The following analyze this problem. In the following Call Traces: " BUG: KASAN: slab-use-after-free in dev_get_flags+0x188/0x1d0 net/core/dev.c:8782 Read of size 4 at addr ffff8880554640b0 by task kworker/1:4/5295 CPU: 1 UID: 0 PID: 5295 Comm: kworker/1:4 Not tainted 6.12.0-rc3-syzkaller-00399-g9197b73fd7bb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: infiniband ib_cache_event_task Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 dev_get_flags+0x188/0x1d0 net/core/dev.c:8782 rxe_query_port+0x12d/0x260 drivers/infiniband/sw/rxe/rxe_verbs.c:60 __ib_query_port drivers/infiniband/core/device.c:2111 [inline] ib_query_port+0x168/0x7d0 drivers/infiniband/core/device.c:2143 ib_cache_update+0x1a9/0xb80 drivers/infiniband/core/cache.c:1494 ib_cache_event_task+0xf3/0x1e0 drivers/infiniband/core/cache.c:1568 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa65/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f2/0x390 kernel/kthread.c:389 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> " 1). In the link [1], " infiniband syz2: set down " This means that on 839.350575, the event ib_cache_event_task was sent andi queued in ib_wq. 2). In the link [1], " team0 (unregistering): Port device team_slave_0 removed " It indicates that before 843.251853, the net device should be freed. 3). In the link [1], " BUG: KASAN: slab-use-after-free in dev_get_flags+0x188/0x1d0 " This means that on 850.559070, this slab-use-after-free problem occurred. In all, on 839.350575, the event ib_cache_event_task was sent and queued in ib_wq, before 843.251853, the net device veth was freed. on 850.559070, this event was executed, and the mentioned freed net device was called. Thus, the above call trace occurred. [1] https://syzkaller.appspot.com/x/log.txt?x=12e7025f980000
CVE-2024-56718 is a vulnerability in the Linux kernel's net/smc subsystem where link down work may execute after the link group (lgr) has been freed, potentially causing a kernel crash due to list corruption. This occurs because the work is scheduled before the lgr is freed but runs afterward without holding a proper reference. The issue has been resolved by ensuring a reference is held before scheduling the work and released after execution or cancellation.
CVE-2024-56658 is a use-after-free vulnerability in the Linux kernel's network namespace dismantling process. The flaw occurs because the 'struct net' is freed prematurely before all destination callbacks are executed, leading to a slab-use-after-free in dst_destroy. This can cause memory corruption and potentially allow an attacker with local privileges to compromise system integrity. The issue was reported by Ilya and affects the xfrm4 and xfrm6 network initialization code paths.