Ryan Hall

A flaw exists in the Opto22 Groov Manage REST API that could allow for remote code execution with root privileges. The issue arises when a POST request is sent to a vulnerable endpoint. The application improperly handles header details from the request, using them to construct commands without sufficient safeguards. This allows an attacker with administrative access to inject and execute arbitrary commands as root. The vulnerable endpoint processes POST requests and utilizes header information to build commands. The vulnerable parameters are within the request headers.

The issue is related to the sbcast subsystem of the Slurm resource management system and is associated with weaknesses in the authentication procedure. This can allow a remote attacker to bypass existing security restrictions. The problem is due to incorrect access control, which enables an attacker to modify their extended group list used with the sbcast subsystem and open files with an unauthorized set of extended groups.

The issue is related to the improper enforcement of message integrity during transmission in a communication channel. This allows attackers to modify RPC traffic in a way that bypasses message hash checks, potentially enabling them to exploit the system. The exploitation of this issue can be done remotely.

The issue is related to incorrect access control due to a slurmd Message Integrity Bypass, allowing an attacker to reuse root-level authentication tokens during interaction with the slurmd process. This bypasses the RPC message hashes that protect against undesired MUNGE credential reuse.

An issue was discovered in SchedMD Slurm due to a double free error, allowing attackers to cause a denial of service or possibly execute arbitrary code.

An issue was discovered in SchedMD Slurm, where a NULL pointer dereference leads to denial of service. This can be exploited by a remote attacker to cause a denial of service.

Name of the Vulnerable Software and Affected Versions: Intel(R) Security Library versions prior to 3.3 Description: The issue is related to a missing release of resource after its effective lifetime in an API, which may allow a privileged user to potentially enable denial of service via network access. Recommendations: For versions prior to 3.3, update to version 3.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Intel(R) Security Library versions prior to 3.3 Description: The issue is related to the use of a cryptographically weak pseudo-random number generator (PRNG) in an API. This may allow an authenticated user to potentially enable information disclosure via network access. Recommendations: For versions prior to 3.3, update to version 3.3 or later to resolve the issue. As a temporary workaround, consider restricting network access to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Intel(R) Security Library versions prior to 3.3 Description: The issue is related to key exchange without entity authentication, which may allow an authenticated user to potentially enable escalation of privilege via network access. Recommendations: For versions prior to 3.3, update to version 3.3 or later to resolve the issue. As a temporary workaround, consider restricting network access to minimize the risk of exploitation.

A flaw was found in dpdk, where a lack of bounds checking when copying `iv data` from the VM guest memory into host memory can lead to a large buffer overflow. This issue poses a threat to data confidentiality and integrity, as well as system availability.

An integer underflow in the `move desc` function can cause large amounts of CPU cycles to be consumed in a long-running loop. An attacker could cause `move desc` to get stuck in a 4,294,967,295-count iteration loop. Depending on how `vhost crypto` is used, this could prevent other VMs or network tasks from being serviced by the busy DPDK lcore for an extended period.

A flaw in dpdk allows an attacker to read significant amounts of host memory due to a lack of validation of attacker-controlled parameters, leading to a buffer over read. The results of the over read are then written back to the guest virtual machine memory, posing a threat to data confidentiality and system availability.

A flaw was found in dpdk where virtio ring descriptors and the data they describe are in a region of memory accessible by both the virtual machine and the host. An attacker in a VM can change the contents of the memory after validation. The highest threat from this issue is to data confidentiality and integrity as well as system availability.

A flaw was found in the `copy data` function due to flawed bounds checking, leading to a buffer overflow. This allows an attacker in a virtual machine to write arbitrary data to any address in the `vhost crypto` application, posing a threat to data confidentiality and integrity, as well as system availability.

The issue is related to a resource leak in the i40e driver, which may allow an authenticated user to potentially enable a denial of service via local access. Exploitation of this issue can cause a disruption in service.

The issue is related to a resource leak in the i40e driver, which may allow an authenticated user to potentially enable a denial of service via local access. This could be exploited to cause a disruption in service.