CVE-2021-3283
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 up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.
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 exec and java task drivers in HashiCorp Nomad up to version 0.12.9 have improper process isolation, allowing a task running on a node to access or interact with processes associated with other tasks on the same node. This breaks task isolation boundaries in multi-tenant Nomad deployments.
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.12.10>= 1.0.0, < 1.0.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 the installed Nomad versionRun `nomad version` or check the nomad binary with `nomad --version`Affected if The version is lower than 0.12.10, or >= 1.0.0 but lower than 1.0.3
-
Confirm the exec or java task driver is in useReview job specifications using `nomad job spec` commands, or inspect running allocations with `nomad alloc status <allocation_id>` to see the task driver typeAffected if Jobs are using the `exec` or `java` task driver type
-
Verify multiple tasks are scheduled on the same nodeRun `nomad node status` to identify nodes, then `nomad node status -verbose <node_id>` or query allocations per node to see if multiple allocations exist on a single nodeAffected if More than one task allocation is running on the same Nomad node
-
Check for cross-task process visibilityFrom within a task container or exec session, attempt to list processes from other task contexts, or review if process namespaces are shared by inspecting the node's cgroup configurationAffected if Processes from other tasks are visible or accessible from a given task context
A node is affected if it runs a Nomad version less than 0.12.10 or between 1.0.0 and 1.0.3, uses the exec or java task driver, and has multiple tasks co-located on the same node where task process isolation is broken.
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.12.101.0.3
Upgrade HashiCorp Nomad to version 0.12.10, 1.0.3, or later to restore proper process isolation between tasks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3283 — 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-2021-3283 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