Page 3 of 14 results (0.008 seconds)

CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0

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: 0

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 •

CVSS: 6.9EPSS: 0%CPEs: 29EXPL: 0

The (1) init.d/slurm and (2) init.d/slurmdbd scripts in SLURM before 2.1.14 place the . (dot) directory in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory. Los scripts (1) init.d/slurm y (2) init.d/slurmdbd en SLURM anterior a v2.1.14 colocan el directorio . (punto) en el LD_LIBRARY_PATH, lo cual permite a usuarios locales conseguir privilegios a través de una biblioteca compartida Troyanizada en el directorio de trabajo actual. • http://secunia.com/advisories/41614 http://sourceforge.net/projects/slurm/files//slurm/version_2.1/2.1.14/RELEASE_NOTES_2.1.14/view http://www.securityfocus.com/bid/43537 •

CVSS: 7.2EPSS: 0%CPEs: 15EXPL: 0

Simple Linux Utility for Resource Management (SLURM) 1.2 and 1.3 before 1.3.14 does not properly set supplementary groups before invoking (1) sbcast from the slurmd daemon or (2) strigger from the slurmctld daemon, which might allow local SLURM users to modify files and gain privileges. Simple Linux Utility for Resource Management (SLURM) v1.2 y v1.3 anteriores a v1.3.14 no fija adecuadamente los grupos suplementarios antes de invocar (1) sbcast del demonio slurmd o (2) strigger del demonio slurmctld, lo cual permitiría a usuarios locales de SLURM modificar ficheros y ganar privilegios. • http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524980 http://secunia.com/advisories/34831 http://sourceforge.net/project/shownotes.php?release_id=676055&group_id=157944 http://www.debian.org/security/2009/dsa-1776 http://www.securityfocus.com/bid/34638 http://www.vupen.com/english/advisories/2009/1128 https://exchange.xforce.ibmcloud.com/vulnerabilities/50126 https://exchange.xforce.ibmcloud.com/vulnerabilities/50127 • CWE-255: Credentials Management Errors •