Vulnerabilities

Improper control of dynamically-managed code resources vulnerability in WebAPI component in Synology DiskStation Manager (DSM) before 7.1.1-42962-8 and 7.2.1-69057-2 and 7.2.2-72806 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote authenticated users to obtain privileges without consent via unspecified vectors.

A security flaw has been discovered in dayrui XunRuiCMS up to 4.7.1. Affected is an unknown function of the file /admind45f74adbd95.php?c=email&m=add of the component Email Setting Handler. Performing manipulation results in server-side request forgery. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

A weakness has been identified in dayrui XunRuiCMS up to 4.7.1. Affected by this vulnerability is an unknown functionality of the file /admind45f74adbd95.php?c=field&m=add&rname=site&rid=1&page=0 of the component Add Display Name Field. Executing manipulation of the argument data[name] can lead to cross site scripting. The attack can be executed remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> af_unix: Initialise scc_index in unix_add_edge().<br /> <br /> Quang Le reported that the AF_UNIX GC could garbage-collect a<br /> receive queue of an alive in-flight socket, with a nice repro.<br /> <br /> The repro consists of three stages.<br /> <br /> 1)<br /> 1-a. Create a single cyclic reference with many sockets<br /> 1-b. close() all sockets<br /> 1-c. Trigger GC<br /> <br /> 2)<br /> 2-a. Pass sk-A to an embryo sk-B<br /> 2-b. Pass sk-X to sk-X<br /> 2-c. Trigger GC<br /> <br /> 3)<br /> 3-a. accept() the embryo sk-B<br /> 3-b. Pass sk-B to sk-C<br /> 3-c. close() the in-flight sk-A<br /> 3-d. Trigger GC<br /> <br /> As of 2-c, sk-A and sk-X are linked to unix_unvisited_vertices,<br /> and unix_walk_scc() groups them into two different SCCs:<br /> <br /> unix_sk(sk-A)-&gt;vertex-&gt;scc_index = 2 (UNIX_VERTEX_INDEX_START)<br /> unix_sk(sk-X)-&gt;vertex-&gt;scc_index = 3<br /> <br /> Once GC completes, unix_graph_grouped is set to true.<br /> Also, unix_graph_maybe_cyclic is set to true due to sk-X&amp;#39;s<br /> cyclic self-reference, which makes close() trigger GC.<br /> <br /> At 3-b, unix_add_edge() allocates unix_sk(sk-B)-&gt;vertex and<br /> links it to unix_unvisited_vertices.<br /> <br /> unix_update_graph() is called at 3-a. and 3-b., but neither<br /> unix_graph_grouped nor unix_graph_maybe_cyclic is changed<br /> because both sk-B&amp;#39;s listener and sk-C are not in-flight.<br /> <br /> 3-c decrements sk-A&amp;#39;s file refcnt to 1.<br /> <br /> Since unix_graph_grouped is true at 3-d, unix_walk_scc_fast()<br /> is finally called and iterates 3 sockets sk-A, sk-B, and sk-X:<br /> <br /> sk-A -&gt; sk-B (-&gt; sk-C)<br /> sk-X -&gt; sk-X<br /> <br /> This is totally fine. All of them are not yet close()d and<br /> should be grouped into different SCCs.<br /> <br /> However, unix_vertex_dead() misjudges that sk-A and sk-B are<br /> in the same SCC and sk-A is dead.<br /> <br /> unix_sk(sk-A)-&gt;scc_index == unix_sk(sk-B)-&gt;scc_index vertex-&gt;out_degree<br /> ^-- 1 in-flight count for sk-B<br /> -&gt; sk-A is dead !?<br /> <br /> The problem is that unix_add_edge() does not initialise scc_index.<br /> <br /> Stage 1) is used for heap spraying, making a newly allocated<br /> vertex have vertex-&gt;scc_index == 2 (UNIX_VERTEX_INDEX_START)<br /> set by unix_walk_scc() at 1-c.<br /> <br /> Let&amp;#39;s track the max SCC index from the previous unix_walk_scc()<br /> call and assign the max + 1 to a new vertex&amp;#39;s scc_index.<br /> <br /> This way, we can continue to avoid Tarjan&amp;#39;s algorithm while<br /> preventing misjudgments.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfrm: delete x-&gt;tunnel as we delete x<br /> <br /> The ipcomp fallback tunnels currently get deleted (from the various<br /> lists and hashtables) as the last user state that needed that fallback<br /> is destroyed (not deleted). If a reference to that user state still<br /> exists, the fallback state will remain on the hashtables/lists,<br /> triggering the WARN in xfrm_state_fini. Because of those remaining<br /> references, the fix in commit f75a2804da39 ("xfrm: destroy xfrm_state<br /> synchronously on net exit path") is not complete.<br /> <br /> We recently fixed one such situation in TCP due to defered freeing of<br /> skbs (commit 9b6412e6979f ("tcp: drop secpath at the same time as we<br /> currently drop dst")). This can also happen due to IP reassembly: skbs<br /> with a secpath remain on the reassembly queue until netns<br /> destruction. If we can&amp;#39;t guarantee that the queues are flushed by the<br /> time xfrm_state_fini runs, there may still be references to a (user)<br /> xfrm_state, preventing the timely deletion of the corresponding<br /> fallback state.<br /> <br /> Instead of chasing each instance of skbs holding a secpath one by one,<br /> this patch fixes the issue directly within xfrm, by deleting the<br /> fallback state as soon as the last user state depending on it has been<br /> deleted. Destruction will still happen when the final reference is<br /> dropped.<br /> <br /> A separate lockdep class for the fallback state is required since<br /> we&amp;#39;re going to lock x-&gt;tunnel while x is locked.

Central Dogma versions before 0.78.0 contain an Open Redirect vulnerability that allows attackers to redirect users to untrusted sites via specially crafted URLs, potentially facilitating phishing attacks and credential theft.

A stored Cross-Site Scripting (XSS) vulnerability has been found in Seafile v12.0.10. This vulnerability allows an attacker to execute arbitrary code in the victim&amp;#39;s browser by storing malicious payloads with POST parámetro &amp;#39;p&amp;#39; in &amp;#39;/api/v2.1/repos/{repo_id}/file/&amp;#39;.

A stored Cross-Site Scripting (XSS) vulnerability has been found in Seafile v12.0.10. This vulnerability allows an attacker to execute arbitrary code in the victim&amp;#39;s browser by storing malicious payloads with PUT parámetro &amp;#39;name&amp;#39; in &amp;#39;/api/v2.1/user/&amp;#39;.

A flaw was found in ansible-collection-community-general. This vulnerability allows for information exposure (IE) of sensitive credentials, specifically plaintext passwords, via verbose output when running Ansible with debug modes. Attackers with access to logs could retrieve these secrets and potentially compromise Keycloak accounts or administrative access.

The Custom Post Type UI plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.18.0. This is due to the plugin not verifying that a user has the required capability to perform actions in the "cptui_process_post_type" function. This makes it possible for authenticated attackers, with subscriber level access and above, to add, edit, or delete custom post types in limited situations.

The Beaver Builder – WordPress Page Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.9.4. This is due to the plugin not properly verifying a user&amp;#39;s authorization in the disable() function. This makes it possible for authenticated attackers, with contributor level access and above, to disable the Beaver Builder layout on arbitrary posts and pages, causing content integrity issues and layout disruption on those pages.

The Clik stats plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `$_SERVER[&amp;#39;PHP_SELF&amp;#39;]` parameter in all versions up to, and including, 0.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.