# CVE-2016-10030: Path traversal in n/a

> A user can assume control of arbitrary files if they can trigger a Prolog script failure, requiring a configured Prolog script to exploit.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DLA-921-1, GHSA-9w2c-9wm9-hvcg, UBUNTU-CVE-2016-10030

## What is CVE-2016-10030?

CVE-2016-10030 is a high-severity path traversal vulnerability in n/a, published on 5 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-10030?

It affects 1 product.


Products: Schedmd Slurm.

## How do I fix CVE-2016-10030?

Upgrade to a fixed version.

## Is CVE-2016-10030 being exploited?

There is no known exploitation of CVE-2016-10030 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-49934](https://insights.sbomify.com/CVE-2023-49934/): SQL injection in n/a (critical 9.8)
- [CVE-2023-49937](https://insights.sbomify.com/CVE-2023-49937/): Use after free in n/a (critical 9.8)
- [CVE-2023-49935](https://insights.sbomify.com/CVE-2023-49935/): Auth bypass in n/a (high 8.8)
- [CVE-2023-49938](https://insights.sbomify.com/CVE-2023-49938/): Privilege escalation in n/a (high 8.2)
- [CVE-2017-15566](https://insights.sbomify.com/CVE-2017-15566/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10030 and fix it if it is affected.

What it is: CVE-2016-10030 is a high-severity path traversal vulnerability in n/a, published on 5 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10030 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-10030/ (Markdown: https://insights.sbomify.com/CVE-2016-10030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10030
- OSV: https://osv.dev/vulnerability/CVE-2016-10030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-10030/
Summaries are generated and may contain mistakes; the official description above is the record.