Skip to content
Fencer Intel
high 7.5

CVE-2019-19316 json

Use of a Broken or Risky Cryptographic Algorithm in Terraform

published 6y ago modified last mo. also GHSA-4rvg-555h-r626 , GHSA-h3p9-wrgx-82cm , GO-2022-0839 , EUVD-2021-1091

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/hashicorp/terraform 0.12.17
  • hashicorp terraform 0.12.17
  • terraform SLE Module for Public Cloud 15 SP1 0.12.19-3.6.1

suse advisories SUSE-SU-2020:0320-1

  • terraform openSUSE Tumbleweed 0.14.10-1.12

opensuse advisories openSUSE-SU-2024:11429-1

Is CVE-2019-19316 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/terraform
<0.12.17
0.12.17

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-20 Improper Input Validation
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.