Sam Thomas

The issue is related to a server-side request forgery (SSRF) vulnerability. It could allow a rogue server on the local network to modify its URL using another DNS address to point back to the loopback adapter, potentially exploiting other vulnerabilities on the local server. This vulnerability is associated with insufficient validation of incoming requests.

An uncontrolled resource consumption issue could arise by sending crafted requests to a service, consuming a large amount of memory and eventually resulting in the service being stopped and restarted. This issue requires the attacker to already have root privileges in order to exploit it. The issue may allow remote attackers to create a denial-of-service condition.

An uncontrolled resource consumption issue could arise by sending crafted requests to a service, consuming a large amount of memory and eventually resulting in the service being stopped and restarted. This issue requires the attacker to already have root privileges in order to exploit it.

An issue was discovered in Western Digital My Cloud OS 5 devices, allowing an attacker to execute code in the context of the root user on a vulnerable CGI file due to improper neutralization of special elements used in a command. This issue could lead to remote code execution.

A Server-Side Request Forgery (SSRF) issue was identified, which could allow a rogue server on the local network to modify its URL to point back to the loopback adapter. This could potentially exploit other vulnerabilities on the local server.

This issue allows local attackers to execute arbitrary code on affected installations. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this issue. The specific flaw exists within the handling of redirections. An attacker can force a redirection to a site that serves malicious content. This can be leveraged in conjunction with other issues to escalate privileges and execute arbitrary code in the context of the current user.

The issue concerns the pointer-validation logic in Occlum for Intel SGX, which can act as a confused deputy. This allows a local attacker to access unauthorized information via side-channel analysis.

A limited Server-Side Request Forgery (SSRF) issue was discovered, allowing an attacker to impersonate a server, bypass access controls, and reach any page on the server. The vulnerability was addressed by creating a whitelist for valid parameters.

A limited authentication bypass issue was discovered, allowing an attacker to achieve remote code execution and escalate privileges on the My Cloud devices. The issue was addressed by changing access token validation logic and rewriting rule logic on PHP scripts.

An issue was discovered that could allow an unauthenticated user to execute privileged commands on the device via a cookie, effectively bypassing NAS Admin authentication. This could be further exploited by an authenticated administrator using an upload endpoint to upload executable PHP scripts.

In WordPress, comments from a post or page could sometimes be seen in the latest comments even if the post or page was not public. This issue is related to the comment-template.php file in the wp-includes directory.

Name of the Vulnerable Software and Affected Versions: Drupal Core versions prior to 8.8.8 Drupal Core versions prior to 8.9.1 Drupal Core version 9.0.1 Description: The issue is related to an arbitrary PHP code execution vulnerability under certain circumstances. An attacker could trick an administrator into visiting a malicious site, resulting in the creation of a carefully named directory on the file system. With this directory in place, an attacker could attempt to brute force a remote code execution vulnerability. This issue is most likely to affect Windows servers. The vulnerability is associated with insufficient authentication of executed requests, which could allow a remote attacker to execute arbitrary code. Recommendations: For Drupal Core versions prior to 8.8.8, update to version 8.8.8 or later. For Drupal Core versions prior to 8.9.1, update to version 8.9.1 or later. For Drupal Core version 9.0.1, update to a version later than 9.0.1. As a temporary workaround, consider restricting access to the file system to minimize the risk of exploitation.

The issue is related to the embed block in the WordPress block editor, which allows users with low privileges to inject unfiltered HTML. When affected posts are viewed by a higher privileged user, this could lead to script execution in the editor/wp-admin. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited.

The issue is related to the injection of JavaScript into media file attachment pages by authenticated users with upload permissions, such as authors. This can lead to script execution in the context of a higher privileged user when the file is viewed by them.

The issue is related to an unintended/open redirect when an arbitrary external link is crafted due to a problem in `wp validate redirect()` and URL sanitization. This could allow a remote attacker to access and compromise confidential data.

The issue is related to a SQL injection vulnerability due to the lack of type casting of a variable in a SQL statement. This vulnerability affects the Featured Articles frontend menutype.

The issue allows a malicious user to upload a file that can trigger a cross-site scripting (XSS) vulnerability under certain circumstances. This is related to the File module/subsystem.

The issue is related to insufficient validation of user input, which can lead to remote code execution when performing file operations on an untrusted phar:// URI. This vulnerability exists in PHP's built-in phar stream wrapper and may affect some Drupal code, including core, contrib, and custom code, that performs file operations on user input without proper validation. The vulnerability is mitigated by the fact that exploiting it typically requires access to administrative permissions or an atypical configuration.

The issue arises from the mishandling of serialized data at phar:// URLs in the wp get attachment thumb file function, located in wp-includes/post.php. This allows contributors to conduct PHP object injection attacks via crafted metadata in a "wp.getMediaItem" XMLRPC call.

The issue allows authors to modify metadata, bypassing intended restrictions on deleting files.