SchedMD vulnerabilities
We track 5 vulnerabilities in SchedMD products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on December 14, 2023.
Latest SchedMD vulnerabilities
- 9.8 Critical severity
Slurm: Double Free
An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. Because of a double free, attackers can cause a denial of service or possibly execute arbitrary code. The fixed versions are 22.05.11, 23.02.7, and 23.11.1.
- 7.5 High severity
Slurm: NULL Pointer Dereference
An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. A NULL pointer dereference leads to denial of service. The fixed versions are 22.05.11, 23.02.7, and 23.11.1.
- 8.8 High severity
An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x.
An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x. There is Incorrect Access Control because of a slurmd Message Integrity Bypass. An attacker can reuse root-level authentication tokens during interaction with the slurmd process. This bypasses the R
- 7.5 High severity
Slurm: Improper Enforcement of Message Integrity During Transmission in a Communication Channel
An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. There is 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. T
- 7.0 High severity
slurm: Concurrent Execution using Shared Resource with Improper Synchronization
SchedMD Slurm 23.02.x before 23.02.6 and 22.05.x before 22.05.10 allows filesystem race conditions for gaining ownership of a file, overwriting a file, or deleting files.