CVSS: 9.8EPSS: 0%CPEs: 10EXPL: 0CVE-2018-7033
https://notcve.org/view.php?id=CVE-2018-7033
SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD. SchedMD Slurm en versiones anteriores a la 17.02.10 y 17.11.x en versiones anteriores a la 17.11.5 permite ataques de inyección SQL contra SlurmDBD. • https://lists.debian.org/debian-lts-announce/2018/04/msg00032.html https://lists.debian.org/debian-lts-announce/2018/07/msg00029.html https://lists.schedmd.com/pipermail/slurm-announce/2018/000006.html https://www.debian.org/security/2018/dsa-4254 https://www.schedmd.com/news.php?id=201 • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2017-15566
https://notcve.org/view.php?id=CVE-2017-15566
Insecure SPANK environment variable handling exists in SchedMD Slurm before 16.05.11, 17.x before 17.02.9, and 17.11.x before 17.11.0rc2, allowing privilege escalation to root during Prolog or Epilog execution. Existe una gestión de variables de entorno SPANK insegura en SchedMD Slurm, en versiones anteriores a la 16.05.11, versiones 17.x anteriores a la 17.02.9 y versiones 17.11.x anteriores a la 17.11.0rc2. Esto permite un escalado de privilegios a root durante la ejecución de Prolog o Epilog. • http://www.securityfocus.com/bid/101675 https://www.debian.org/security/2017/dsa-4023 https://www.schedmd.com/news.php?id=193#OPT_193 • CWE-426: Untrusted Search Path •
CVSS: 8.1EPSS: 0%CPEs: 15EXPL: 0CVE-2016-10030
https://notcve.org/view.php?id=CVE-2016-10030
The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 ("success") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. • http://www.securityfocus.com/bid/95299 https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee https://www.schedmd.com/news.php?id=178 • CWE-284: Improper Access Control •