Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> eventpoll: don&amp;#39;t decrement ep refcount while still holding the ep mutex<br /> <br /> Jann Horn points out that epoll is decrementing the ep refcount and then<br /> doing a<br /> <br /> mutex_unlock(&amp;ep-&gt;mtx);<br /> <br /> afterwards. That&amp;#39;s very wrong, because it can lead to a use-after-free.<br /> <br /> That pattern is actually fine for the very last reference, because the<br /> code in question will delay the actual call to "ep_free(ep)" until after<br /> it has unlocked the mutex.<br /> <br /> But it&amp;#39;s wrong for the much subtler "next to last" case when somebody<br /> *else* may also be dropping their reference and free the ep while we&amp;#39;re<br /> still using the mutex.<br /> <br /> Note that this is true even if that other user is also using the same ep<br /> mutex: mutexes, unlike spinlocks, can not be used for object ownership,<br /> even if they guarantee mutual exclusion.<br /> <br /> A mutex "unlock" operation is not atomic, and as one user is still<br /> accessing the mutex as part of unlocking it, another user can come in<br /> and get the now released mutex and free the data structure while the<br /> first user is still cleaning up.<br /> <br /> See our mutex documentation in Documentation/locking/mutex-design.rst,<br /> in particular the section [1] about semantics:<br /> <br /> "mutex_unlock() may access the mutex structure even after it has<br /> internally released the lock already - so it&amp;#39;s not safe for<br /> another context to acquire the mutex and assume that the<br /> mutex_unlock() context is not using the structure anymore"<br /> <br /> So if we drop our ep ref before the mutex unlock, but we weren&amp;#39;t the<br /> last one, we may then unlock the mutex, another user comes in, drops<br /> _their_ reference and releases the &amp;#39;ep&amp;#39; as it now has no users - all<br /> while the mutex_unlock() is still accessing it.<br /> <br /> Fix this by simply moving the ep refcount dropping to outside the mutex:<br /> the refcount itself is atomic, and doesn&amp;#39;t need mutex protection (that&amp;#39;s<br /> the whole _point_ of refcounts: unlike mutexes, they are inherently<br /> about object lifetimes).

An improper access control vulnerability [CWE-284] in FortiIsolator version 2.4.4, version 2.4.3, 2.3 all versions logging component may allow a remote authenticated read-only attacker to alter logs via a crafted HTTP request.

An insufficient session expiration vulnerability [CWE-613] in FortiSandbox FortiSandbox version 4.4.4 and below, version 4.2.6 and below, 4.0 all versions, 3.2 all versions and FortiIsolator version 2.4 and below, 2.3 all versions, 2.2 all versions, 2.1 all versions, 2.0 all versions, 1.2 all versions may allow a remote attacker in possession of an admin session cookie to keep using that admin&amp;#39;s session even after the admin user was deleted.

The Malcure Malware Scanner — #1 Toolset for WordPress Malware Removal plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 16.8 via the wpmr_inspect_file() function due to a missing capability check. This makes it possible for authenticated attackers, with subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

The MasterStudy LMS Pro plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the &amp;#39;install_and_activate_plugin&amp;#39; function in all versions up to, and including, 4.7.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site&amp;#39;s server which may make remote code execution possible. The vulnerability is difficult to exploit due to timing requirements and environmental factors.

The Attachment Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the handle_actions() function in all versions up to, and including, 2.1.2. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

The B1.lt plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;id&amp;#39; parameter in all versions up to, and including, 2.2.56 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The B1.lt plugin for WordPress is vulnerable to SQL Injection due to a missing capability check on the b1_run_query AJAX action in all versions up to, and including, 2.2.56. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute and run arbitrary SQL commands.

The Terms descriptions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.4.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

The Block Editor Gallery Slider plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the classic_gallery_slider_options() function in all versions up to, and including, 1.1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update limited post meta for arbitrary posts.

The Crowdfunding for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘width’ parameter in all versions up to, and including, 3.1.14 due to insufficient input sanitization and output escaping. 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.

The Testimonial Post type plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘auto_play’ parameter in all versions up to, and including, 1.2.1 due to insufficient input sanitization and output escaping. 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.