Improper Access Control Affecting slurm-llnl package, versions <15.08.7-1ubuntu0.1~esm3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Access Control vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UBUNTU1604-SLURMLLNL-299783
- published5 Jan 2017
- disclosed5 Jan 2017
Introduced: 5 Jan 2017
CVE-2016-10030 (opens in a new tab)How to fix?
Upgrade Ubuntu:16.04 slurm-llnl to version 15.08.7-1ubuntu0.1~esm3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream slurm-llnl package and not the slurm-llnl package as distributed by Ubuntu.
See How to fix? for Ubuntu:16.04 relevant fixed versions and status.
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. If you do not have a Prolog set you are unaffected by this issue.