Remote Code Execution

This vulnerability allows an attacker to potentially crash the ImageMagick software or execute arbitrary code by exploiting a flaw in how images are handled, specifically when a cloned image is improperly destroyed. It affects versions prior to 7.1.2-16 and 6.9.13-41, so users running older versions are at risk if they process untrusted image files.

An attacker can exploit a flaw in ImageMagick's MSL file processing to access and manipulate freed memory, potentially leading to crashes or arbitrary code execution if they can get a user to open a specially crafted MSL file. This vulnerability affects versions before 7.1.2-16 and 6.9.13-41, so updating to these versions or later is essential for protection.

This vulnerability allows an attacker to potentially execute malicious code on a system running vulnerable versions of ImageMagick by sending specially crafted PCL files, which can cause the software to crash or behave unexpectedly. To exploit this, the attacker needs access to a system where ImageMagick processes these files, making it important for users to update to the fixed versions to protect against this risk.

This vulnerability allows an attacker to crash the ImageMagick software or potentially execute malicious code by sending specially crafted image processing requests that exceed the expected size limits. It affects versions prior to 7.1.2-16 and 6.9.13-41, so users running older versions are at risk if they process untrusted image data.

An attacker can exploit a vulnerability in ImageMagick to manipulate specially crafted images, potentially causing the software to crash or execute malicious code. This issue affects versions prior to 7.1.2-16, so updating to this version or later is essential to protect against it.

This vulnerability allows an attacker to import other users' data from Misskey servers, but they need to know the specific ID of the file they want to access. While the risk is considered low, it still poses a potential privacy issue for users on affected versions of the platform.

An attacker can bypass security checks that verify the authenticity of messages sent between Misskey servers, which could allow them to send fake or malicious content. This vulnerability affects all Misskey servers, regardless of whether they are set up to communicate with other servers or not, and it has been fixed in the latest version.

This vulnerability allows attackers to access sensitive data on Misskey servers that they shouldn't be able to see, potentially leading to a major data breach. It affects all versions from 8.45.0 up to, but not including, 2026.3.1, regardless of whether the server's federation feature is turned on.

This vulnerability allows an unprivileged user to crash the operating system by exploiting a flaw in the way routing information is handled, leading to a stack overflow. While the crash is a protective measure, it could potentially be bypassed by other vulnerabilities, allowing an attacker to gain higher privileges on the system.

An attacker can exploit this vulnerability to gain unauthorized write access to protected memory areas, potentially allowing them to modify sensitive data. This can happen when the software is running as a non-privileged user and improperly handles memory protections, making it easier for attackers to manipulate the system.

An attacker can gain unauthorized access to sensitive patient information by exploiting a flaw in the queue management system's patient search feature, which can be done remotely. This vulnerability requires no special access or credentials, making it easier for malicious users to take advantage of it.

This vulnerability allows an attacker to inject malicious scripts into the payroll management system, potentially compromising user data or session information. It can be exploited remotely by manipulating a specific part of the web application without needing special access or credentials.

An attacker can exploit a flaw in the universal BACnet router firmware to upload and apply any type of data, such as malicious files or sensitive configuration settings, without proper authorization. This can happen remotely through a specific web endpoint, meaning the attacker doesn’t need physical access to the device.

An attacker can remotely upload and install malicious updates on the universal BACnet router firmware because the system does not properly check if they are authorized to do so. This means that anyone with access to the specific update endpoint can take control of the device without needing any special permissions.

This vulnerability allows a low-privileged remote attacker to download sensitive files, such as system backups and certificate requests, from the device. The attacker can exploit this by accessing a specific web endpoint without needing high-level permissions.

This vulnerability allows an attacker to bypass security measures by sending any network traffic through the universal BACnet router, even if an administrator tries to block it with an empty filter list. The issue arises because the router does not enforce restrictions when the filter is empty, meaning no special conditions are needed for an attacker to exploit this flaw.

This vulnerability allows an attacker to inject malicious scripts into the web-based pharmacy management system, potentially compromising user data and session information. It can be exploited remotely by manipulating the "fullname" field in the profile editing function, making it a risk for any user interacting with the system.

This vulnerability allows an attacker to remotely manipulate the university management system's database by exploiting a flaw in a specific file, which can lead to unauthorized access to sensitive information. The attacker needs to send a specially crafted request to the system, and there are publicly available tools that can facilitate this exploit.

This vulnerability allows an attacker to gain unauthorized access to the client database management system, potentially letting them modify user information without proper permissions. The attack can be carried out remotely, meaning the attacker doesn't need physical access to the system, and it has been publicly disclosed, making it easier for malicious actors to exploit it.

An attacker can gain unauthorized access to delete a manager from the client database management system by manipulating a specific ID in the system's code. This can be done remotely, meaning the attacker doesn't need to be on the same network as the target system.