When 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.
When 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.
When 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.
When 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.
### Specific Go Packages Affected
github.com/hashicorp/terraform/backend/remote-state/azure
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Dec 2, 2019, 8:50:44 PM
dateUpdated: Aug 5, 2024, 2:16:46 AM
2 related source bulletins · separate from aliases
openSUSE-SU-2024:11429-1: terraform-0.14.10-1.12 on GA media
CVE-2019-19316
SUSE-SU-2020:0320-1: Security update for terraform
CVE-2019-19316
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-319
Original publisher date fields
published: 2019-12-02T21:15:16.810
lastModified: 2026-06-17T02:26:29.530
1 source CPE criteria · context only
cpe:2.3:a:hashicorp:terraform:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.