Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> team: Move team device type change at the end of team_port_add<br /> <br /> Attempting to add a port device that is already up will expectedly fail,<br /> but not before modifying the team device header_ops.<br /> <br /> In the case of the syzbot reproducer the gre0 device is<br /> already in state UP when it attempts to add it as a<br /> port device of team0, this fails but before that<br /> header_ops-&gt;create of team0 is changed from eth_header to ipgre_header<br /> in the call to team_dev_type_check_change.<br /> <br /> Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense<br /> as the private data of the device still holds a struct team.<br /> <br /> Example sequence of iproute2 commands to reproduce the hang/BUG():<br /> ip link add dev team0 type team<br /> ip link add dev gre0 type gre<br /> ip link set dev gre0 up<br /> ip link set dev gre0 master team0<br /> ip link set dev team0 up<br /> ping -I team0 1.1.1.1<br /> <br /> Move team_dev_type_check_change down where all other checks have passed<br /> as it changes the dev type with no way to restore it in case<br /> one of the checks that follow it fail.<br /> <br /> Also make sure to preserve the origial mtu assignment:<br /> - If port_dev is not the same type as dev, dev takes mtu from port_dev<br /> - If port_dev is the same type as dev, port_dev takes mtu from dev<br /> <br /> This is done by adding a conditional before the call to dev_set_mtu<br /> to prevent it from assigning port_dev-&gt;mtu = dev-&gt;mtu and instead<br /> letting team_dev_type_check_change assign dev-&gt;mtu = port_dev-&gt;mtu.<br /> The conditional is needed because the patch moves the call to<br /> team_dev_type_check_change past dev_set_mtu.<br /> <br /> Testing:<br /> - team device driver in-tree selftests<br /> - Add/remove various devices as slaves of team device<br /> - syzbot

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> veth: reduce XDP no_direct return section to fix race<br /> <br /> As explain in commit fa349e396e48 ("veth: Fix race with AF_XDP exposing<br /> old or uninitialized descriptors") for veth there is a chance after<br /> napi_complete_done() that another CPU can manage start another NAPI<br /> instance running veth_pool(). For NAPI this is correctly handled as the<br /> napi_schedule_prep() check will prevent multiple instances from getting<br /> scheduled, but for the remaining code in veth_pool() this can run<br /> concurrent with the newly started NAPI instance.<br /> <br /> The problem/race is that xdp_clear_return_frame_no_direct() isn&amp;#39;t<br /> designed to be nested.<br /> <br /> Prior to commit 401cb7dae813 ("net: Reference bpf_redirect_info via<br /> task_struct on PREEMPT_RT.") the temporary BPF net context<br /> bpf_redirect_info was stored per CPU, where this wasn&amp;#39;t an issue. Since<br /> this commit the BPF context is stored in &amp;#39;current&amp;#39; task_struct. When<br /> running veth in threaded-NAPI mode, then the kthread becomes the storage<br /> area. Now a race exists between two concurrent veth_pool() function calls<br /> one exiting NAPI and one running new NAPI, both using the same BPF net<br /> context.<br /> <br /> Race is when another CPU gets within the xdp_set_return_frame_no_direct()<br /> section before exiting veth_pool() calls the clear-function<br /> xdp_clear_return_frame_no_direct().

Rejected reason: This CVE id was assigned to an issue which was later deemed not security relevant.

Improper Neutralization of Input During Web Page Generation (XSS or &amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Hotech Software Inc. Otello allows Stored XSS.<br /> <br /> This issue affects Otello: from 2.4.0 before 2.4.4.

Missing Authorization vulnerability in VillaTheme HAPPY happy-helpdesk-support-ticket-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects HAPPY: from n/a through

Missing Authorization vulnerability in Vikas Ratudi Chakra test chakra-test allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Chakra test: from n/a through

Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in CodexThemes TheGem Theme Elements (for Elementor) thegem-elements-elementor.This issue affects TheGem Theme Elements (for Elementor): from n/a through

Improper Control of Filename for Include/Require Statement in PHP Program (&amp;#39;PHP Remote File Inclusion&amp;#39;) vulnerability in CodexThemes TheGem Theme Elements (for Elementor) thegem-elements-elementor.This issue affects TheGem Theme Elements (for Elementor): from n/a through

Improper Neutralization of Special Elements used in an SQL Command (&amp;#39;SQL Injection&amp;#39;) vulnerability in Ruben Garcia AutomatorWP automatorwp allows SQL Injection.This issue affects AutomatorWP: from n/a through

Improper input validation at one of the endpoints of Eaton xComfort ECI&amp;#39;s <br /> <br /> web interface, could lead into an attacker with network access to the device executing privileged user commands. As cybersecurity<br /> standards continue to evolve and to meet our requirements today, Eaton has decided to discontinue the<br /> product. Upon retirement or end of support, there will be no new security updates, non-security<br /> updates, or paid assisted support options, or online technical content updates.

Improper Control of Filename for Include/Require Statement in PHP Program (&amp;#39;PHP Remote File Inclusion&amp;#39;) vulnerability in thembay Diza diza allows PHP Local File Inclusion.This issue affects Diza: from n/a through

Improper Control of Filename for Include/Require Statement in PHP Program (&amp;#39;PHP Remote File Inclusion&amp;#39;) vulnerability in thembay Nika nika allows PHP Local File Inclusion.This issue affects Nika: from n/a through