TerraformApplication · Hashicorp
CVE-2019-19316
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 · uneditedWhen using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.
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 confidenceIn Terraform versions prior to 0.12.17, when using the Azure backend with a shared access signature (SAS), the SAS token and state snapshot may be transmitted over unencrypted HTTP instead of HTTPS, allowing potential interception of sensitive authentication credentials and state data in transit.
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
TerraformApplication
< 0.12.17CVSS 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 installed Terraform versionRun `terraform version` on the system running Terraform configurationsAffected if The version shown is prior to 0.12.17 (e.g., 0.12.16, 0.12.0, etc.)
-
Locate Terraform backend configurationSearch for `.tf` files containing `backend "azurerm"` or inspect `terraform.tfstate` backend configurationAffected if The configuration uses the Azure (azurerm) backend for state storage
-
Inspect backend authentication methodExamine the backend block in your Terraform configuration for `sas_token` parameter or check if `use_msi` is not set to trueAffected if The Azure backend is configured with `sas_token` instead of managed identity (use_msi) or storage account key, and the Terraform version is below 0.12.17
-
Verify network traffic to Azure storageUse network capture tools (e.g., Wireshark, tcpdump) or Azure Storage Analytics logs to inspect outbound connections from the Terraform host to Azure storage endpointsAffected if HTTP (port 80) traffic is observed to Azure Blob Storage endpoints when using SAS token authentication with vulnerable Terraform versions
A user is affected if they run Terraform versions prior to 0.12.17 AND use the Azure backend with SAS token authentication, resulting in unencrypted HTTP connections to Azure storage.
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.17
Upgrade Terraform to version 0.12.17 or later to resolve the cleartext transmission issue; alternatively, ensure network-level controls enforce HTTPS for Azure storage communications.
Fix this in Terraform
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19316 — 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-19316 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