# CVE-2020-28348: Path Traversal in HashiCorp Nomad > Attackers can subvert the Docker file sandbox in HashiCorp Nomad via volume mounts, potentially escaping the container to execute code or escalate privileges. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-5x92-p4p5-33c4, GO-2022-0770 ## What is CVE-2020-28348? CVE-2020-28348 is a medium-severity path traversal vulnerability in n/a, published on 24 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description HashiCorp Nomad and Nomad Enterprise 0.9.0 up to 0.12.7 client Docker file sandbox feature may be subverted when not explicitly disabled or when using a volume mount type. Fixed in 0.12.8, 0.11.7, and 0.10.8. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2020-28348? 7 open source packages ship an affected version, including github.com/hashicorp/nomad. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/hashicorp/nomad` | Go | From 0.11.0-beta1 | 0.11.7 | | `github.com/hashicorp/nomad` | Go | From 0.11.0-beta1 | 0.11.7 | | `github.com/hashicorp/nomad` | Go | From 0.12.0-beta1 | 0.12.8 | | `github.com/hashicorp/nomad` | Go | From 0.12.0-beta1 | 0.12.8 | | `github.com/hashicorp/nomad` | Go | From 0.9.0 | 0.10.8, 0.11.7, 0.12.8 | | `github.com/hashicorp/nomad` | Go | From 0.9.0 | 0.10.8 | | `github.com/hashicorp/nomad` | Go | From 0.9.0 | 0.10.8 | Products: Hashicorp Nomad. ## How do I fix CVE-2020-28348? Upgrade github.com/hashicorp/nomad to a fixed version for your release line: 0.11.7, 0.12.8 or 0.10.8. ## Is CVE-2020-28348 being exploited? There is no known exploitation of CVE-2020-28348 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2023-1782](https://insights.sbomify.com/CVE-2023-1782/): Nomad Unauthenticated Client Agent HTTP Request Privilege Escalation (critical 10.0) - [CVE-2022-30324](https://insights.sbomify.com/CVE-2022-30324/): Privilege escalation in Hashicorp Nomad (critical 9.8) - [CVE-2020-7956](https://insights.sbomify.com/CVE-2020-7956/): Improper Certificate Validation in HashiCorp Nomad (critical 9.8) - [CVE-2019-12618](https://insights.sbomify.com/CVE-2019-12618/): Hashicorp Nomad Access Control Issues (critical 9.8) - [CVE-2020-27195](https://insights.sbomify.com/CVE-2020-27195/): Use After Free in HashiCorp Nomad (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-28348 and fix it if it is affected. What it is: CVE-2020-28348 is a medium-severity path traversal vulnerability in n/a, published on 24 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-28348 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/hashicorp/nomad (Go): affected from 0.11.0-beta1; fixed in 0.11.7 - github.com/hashicorp/nomad (Go): affected from 0.11.0-beta1; fixed in 0.11.7 - github.com/hashicorp/nomad (Go): affected from 0.12.0-beta1; fixed in 0.12.8 - github.com/hashicorp/nomad (Go): affected from 0.12.0-beta1; fixed in 0.12.8 - github.com/hashicorp/nomad (Go): affected from 0.9.0; fixed in 0.10.8, 0.11.7, 0.12.8 - github.com/hashicorp/nomad (Go): affected from 0.9.0; fixed in 0.10.8 - github.com/hashicorp/nomad (Go): affected from 0.9.0; fixed in 0.10.8 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-2020-28348/ (Markdown: https://insights.sbomify.com/CVE-2020-28348/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-28348 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-28348 - OSV: https://osv.dev/vulnerability/CVE-2020-28348 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-28348/ Summaries are generated and may contain mistakes; the official description above is the record.