CVE-2019-14802
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 0.5.0 through 0.9.4 (fixed in 0.9.5) reveals unintended environment variables to the rendering task during template rendering, aka GHSA-6hv3-7c34-4hx8. This applies to nomad/client/allocrunner/taskrunner/template.
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 confidenceHashiCorp Nomad versions 0.5.0 through 0.9.4 contain a vulnerability in the template rendering subsystem (nomad/client/allocrunner/taskrunner/template) where environment variables not intended for a task are inadvertently exposed during template rendering. This environment variable leakage could allow a task to access sensitive variables from the host or Nomad agent that should not have been accessible.
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.5.0, < 0.9.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Determine installed Nomad versionRun 'nomad version' to retrieve the client and server version informationAffected if The version listed is >= 0.5.0 and < 0.9.5
-
Identify jobs using template stanzasReview job specification files for the 'template' stanza, or query the Nomad API at /v1/jobs to list all registered jobs and inspect their task configurationsAffected if Any job definition contains a template stanza that uses environment variables
-
Inspect rendered environment variablesFrom within a task using templates, render a template to inspect all available environment variables (for example, using a template that outputs {{env ""}} to list all vars)Affected if The output includes environment variables from the host or Nomad agent that were not explicitly configured for that task (such as NOMAD_ADDR, NOMAD_SECRET_ID, or host-level variables not intended for the task)
A user is affected if they run Nomad version 0.5.0 through 0.9.4 and have jobs using the template stanza that could inadvertently receive sensitive host or agent environment variables.
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.
dbcve · scoped0.9.5
Upgrade HashiCorp Nomad to version 0.9.5 or later to remediate this vulnerability.
0.9.5 or later
- Back up your Nomad configuration files and any persistent data
- Stop the Nomad service on all nodes in the cluster
- Download and install HashiCorp Nomad version 0.9.5 or later from the official releases (www.hashicorp.com/downloads)
- Verify the checksum of the downloaded package matches the published hash
- Replace the existing Nomad binary with the new version on all cluster nodes
- Restart the Nomad service on all nodes
- Verify the cluster is healthy using 'nomad server members' and 'nomad nodes status'
- Confirm template rendering no longer exposes unintended environment variables
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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 $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14802 — 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-2019-14802 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