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.
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product’s direct control.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Slurm | Schedmd | * | 16.05.11 (excluding) |
| Slurm | Schedmd | 17.02.0 (including) | 17.2.09 (excluding) |
| Slurm | Schedmd | 17.11.0-rc1 (including) | 17.11.0-rc1 (including) |
| Slurm-llnl | Ubuntu | artful | * |
| Slurm-llnl | Ubuntu | esm-apps/xenial | * |
| Slurm-llnl | Ubuntu | upstream | * |
| Slurm-llnl | Ubuntu | xenial | * |
| Slurm-llnl | Ubuntu | zesty | * |
This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the product uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted product would then execute. The problem extends to any type of critical resource that the product trusts. Some of the most common variants of untrusted search path are: