Docker hashicorp/terraform:0.12.10

Vulnerabilities

27 via 37 paths

Dependencies

30

Source

Group 6 Copy Created with Sketch. Docker

Target OS

alpine:3.10.2
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 20
  • 5
  • 2
Status
  • 27
  • 0
  • 0

high severity

Arbitrary Code Injection

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.66.0-r0
  • Fixed in: 7.66.0-r1

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* curl/libcurl@7.66.0-r0

Overview

Affected versions of this package are vulnerable to Arbitrary Code Injection curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.

Remediation

Upgrade curl to version or higher.

References

high severity

Improper Certificate Validation

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.66.0-r0
  • Fixed in: 7.66.0-r3

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* curl/libcurl@7.66.0-r0

Overview

Affected versions of this package are vulnerable to Improper Certificate Validation curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.

Remediation

Upgrade curl to version or higher.

References

high severity

Information Exposure

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.66.0-r0
  • Fixed in: 7.66.0-r1

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* curl/libcurl@7.66.0-r0

Overview

Affected versions of this package are vulnerable to Information Exposure curl 7.62.0 through 7.70.0 is vulnerable to an information disclosure vulnerability that can lead to a partial password being leaked over the network and to the DNS server(s).

Remediation

Upgrade curl to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.66.0-r0
  • Fixed in: 7.66.0-r3

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* curl/libcurl@7.66.0-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

Remediation

Upgrade curl to version or higher.

References

high severity

Use After Free

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.66.0-r0
  • Fixed in: 7.66.0-r2

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* curl/libcurl@7.66.0-r0

Overview

Affected versions of this package are vulnerable to Use After Free. Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.

Remediation

Upgrade curl to version or higher.

References

high severity

CVE-2019-1353

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to CVE-2019-1353. An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. When running Git in the Windows Subsystem for Linux (also known as "WSL") while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x before 2.24.1 because a "git submodule update" operation can run commands found in the .gitmodules file of a malicious repository.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1352, CVE-2019-1387.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

Remediation

Upgrade git to version or higher.

References

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.4-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials. Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. This bug is similar to CVE-2020-5260(GHSA-qm7j-c969-7j4q). The fix for that bug still left the door open for an exploit where some credential is leaked (but the attacker cannot control which one). Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that are considered illegal as of the recently published Git versions can cause Git to send a "blank" pattern to helpers, missing hostname and protocol fields. Many helpers will interpret this as matching any URL, and will return some unspecified stored password, leaking the password to an attacker's server. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The root of the problem is in Git itself, which should not be feeding blank input to helpers. However, the ability to exploit the vulnerability in practice depends on which helpers are in use. Credential helpers which are known to trigger the vulnerability: - Git's "store" helper - Git's "cache" helper - the "osxkeychain" helper that ships in Git's "contrib" directory Credential helpers which are known to be safe even with vulnerable versions of Git: - Git Credential Manager for Windows Any helper not in this list should be assumed to trigger the vulnerability.

Remediation

Upgrade git to version or higher.

References

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.3-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials. Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.3, 2.21.2, 2.22.3, 2.23.2, 2.24.2, 2.25.3, 2.26.1.

Remediation

Upgrade git to version or higher.

References

high severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Use of Incorrectly-Resolved Name or Reference. A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

Remediation

Upgrade git to version or higher.

References

high severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.39.2-r0
  • Fixed in: 1.39.2-r1

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* nghttp2/nghttp2-libs@1.39.2-r0

Overview

Affected versions of this package are vulnerable to Improper Enforcement of Message or Data Structure. In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.

Remediation

Upgrade nghttp2 to version or higher.

References

high severity
new

Inadequate Encryption Strength

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1j-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to Inadequate Encryption Strength. OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed to use a special form of padding. A server that supports greater than SSLv2 is supposed to reject connection attempts from a client where this special form of padding is present, because this indicates that a version rollback has occurred (i.e. both client and server support greater than SSLv2, and yet this is the version that is being requested). The implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present, and rejected if it is absent. This means that such as server will accept a connection if a version rollback attack has occurred. Further the server will erroneously reject a connection if a normal SSLv2 connection attempt is made. Only OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by this issue. In order to be vulnerable a 1.0.2 server must: 1) have configured SSLv2 support at compile time (this is off by default), 2) have configured SSLv2 support at runtime (this is off by default), 3) have configured SSLv2 ciphersuites (these are not in the default ciphersuite list) OpenSSL 1.1.1 does not have SSLv2 support and therefore is not vulnerable to this issue. The underlying error is in the implementation of the RSA_padding_check_SSLv23() function. This also affects the RSA_SSLV23_PADDING padding mode used by various other functions. Although 1.1.1 does not support SSLv2 the RSA_padding_check_SSLv23() function still exists, as does the RSA_SSLV23_PADDING padding mode. Applications that directly call that function or use that padding mode will encounter this issue. However since there is no support for the SSLv2 protocol in 1.1.1 this is considered a bug and not a security issue in that version. OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.0.2y (Affected 1.0.2s-1.0.2x).

Remediation

Upgrade openssl to version or higher.

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1j-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl to version or higher.

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1j-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl to version or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1g-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

Remediation

Upgrade openssl to version or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.22-r3 and musl/musl-utils@1.1.22-r3
  • Fixed in: 1.1.22-r4

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* musl/musl@1.1.22-r3
  • Introduced through: hashicorp/terraform:0.12.10@* musl/musl-utils@1.1.22-r3

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. In musl libc through 1.2.1, wcsnrtombs mishandles particular combinations of destination buffer size and source character limit, as demonstrated by an invalid write access (buffer overflow).

Remediation

Upgrade musl to version or higher.

References

medium severity

Information Exposure

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1d-r2

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to Information Exposure. There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

Remediation

Upgrade openssl to version or higher.

References

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1i-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

Remediation

Upgrade openssl to version or higher.

References

medium severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

References

low severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.22.0-r0
  • Fixed in: 2.22.2-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* git/git@2.22.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths.

Remediation

Upgrade git to version or higher.

References

low severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1c-r0 and openssl/libssl1.1@1.1.1c-r0
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libcrypto1.1@1.1.1c-r0
  • Introduced through: hashicorp/terraform:0.12.10@* openssl/libssl1.1@1.1.1c-r0

Overview

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References