CVE-2020-28348
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHashiCorp 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Docker file sandbox feature in HashiCorp Nomad (versions 0.9.0-0.12.7) can be subverted, allowing containers to potentially escape isolation. The sandbox is designed to restrict container file system access but can be bypassed either when not explicitly enabled/disabled or when using certain volume mount types, enabling unauthorized file system access from within containers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.9.0, < 0.10.8>= 0.11.0, < 0.11.7>= 0.12.0, < 0.12.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Nomad versionRun `nomad version` or check the Nomad binary versionAffected if Version is >= 0.9.0 and < 0.10.8, OR >= 0.11.0 and < 0.11.7, OR >= 0.12.0 and < 0.12.8
-
Locate Nomad agent configuration fileFind the Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or /etc/nomad.conf)Affected if Configuration file exists and is being used by Nomad agents
-
Check Docker file sandbox configurationInspect the Nomad configuration for `docker.file_sandbox` setting under the plugin stanza. Run: `grep -r 'file_sandbox' /etc/nomad.d/` or examine the configuration manuallyAffected if The file_sandbox setting is absent, not explicitly set to true or false, or is present with certain vulnerable volume mount types in use
-
Identify Docker volume mounts in Nomad job specificationsReview all Nomad job files (*.nomad) and running job specifications via `nomad job status` for host_path volume mounts. Run `nomad job inspect <job_id>` to see volume configurationsAffected if Jobs use host_path volume mounts that could bypass the file sandbox isolation
A system is affected if running a vulnerable Nomad version AND the Docker file sandbox is not explicitly configured (missing or unset) AND vulnerable volume mount types are in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.10.80.11.70.12.8
Upgrade Nomad to version 0.12.8, 0.11.7, or 0.10.8 (or later). If upgrading is not immediately feasible, explicitly configure the Docker file sandbox and avoid using the vulnerable volume mount type referenced in the security advisory.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-28348 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data