Docker google/cloud-sdk:258.0.0-alpine

Vulnerabilities

47 via 60 paths

Dependencies

55

Source

Group 6 Copy Created with Sketch. Docker

Target OS

alpine:3.9.2
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 34
  • 9
  • 4
Status
  • 47
  • 0
  • 0

high severity

Arbitrary Code Injection

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.64.0-r2 and curl/libcurl@7.64.0-r2
  • Fixed in: 7.64.0-r4

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/curl@7.64.0-r2
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/libcurl@7.64.0-r2

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

Buffer Overflow

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.64.0-r2 and curl/libcurl@7.64.0-r2
  • Fixed in: 7.64.0-r3

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/curl@7.64.0-r2
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/libcurl@7.64.0-r2

high severity

Double Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.64.0-r2 and curl/libcurl@7.64.0-r2
  • Fixed in: 7.64.0-r3

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/curl@7.64.0-r2
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/libcurl@7.64.0-r2

high severity

Information Exposure

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.64.0-r2 and curl/libcurl@7.64.0-r2
  • Fixed in: 7.64.0-r4

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/curl@7.64.0-r2
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/libcurl@7.64.0-r2

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

Use After Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.64.0-r2 and curl/libcurl@7.64.0-r2
  • Fixed in: 7.66.0-r5

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/curl@7.64.0-r2
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* curl/libcurl@7.64.0-r2

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

Out-of-bounds Write

  • Vulnerable module: cyrus-sasl/libsasl
  • Introduced through: cyrus-sasl/libsasl@2.1.27-r1
  • Fixed in: 2.1.27-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* cyrus-sasl/libsasl@2.1.27-r1

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write cyrus-sasl (aka Cyrus SASL) 2.1.27 has an out-of-bounds write leading to unauthenticated remote denial-of-service in OpenLDAP via a malformed LDAP packet. The OpenLDAP crash is ultimately caused by an off-by-one error in _sasl_add_string in common.c in cyrus-sasl.

Remediation

Upgrade cyrus-sasl to version or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: expat/expat
  • Introduced through: expat/expat@2.2.7-r0
  • Fixed in: 2.2.7-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* expat/expat@2.2.7-r0

Overview

In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.

References

high severity

CVE-2019-1353

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.4-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.3-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg/gnupg
  • Introduced through: gnupg/gnupg@2.2.12-r0
  • Fixed in: 2.2.19-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* gnupg/gnupg@2.2.12-r0

Overview

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm. A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.

Remediation

Upgrade gnupg to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: gnutls/gnutls
  • Introduced through: gnutls/gnutls@3.6.7-r0
  • Fixed in: 3.6.15-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* gnutls/gnutls@3.6.7-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. An issue was discovered in GnuTLS before 3.6.15. A server can trigger a NULL pointer dereference in a TLS 1.3 client if a no_renegotiation alert is sent with unexpected timing, and then an invalid second handshake occurs. The crash happens in the application's error handling path, where the gnutls_deinit function is called after detecting a handshake failure.

Remediation

Upgrade gnutls to version or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls/gnutls
  • Introduced through: gnutls/gnutls@3.6.7-r0
  • Fixed in: 3.6.14-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* gnutls/gnutls@3.6.7-r0

Overview

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm. GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TLS server always uses wrong data in place of an encryption key derived from an application.

Remediation

Upgrade gnutls to version or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnutls/gnutls
  • Introduced through: gnutls/gnutls@3.6.7-r0
  • Fixed in: 3.6.7-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* gnutls/gnutls@3.6.7-r0

Overview

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm. GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.

Remediation

Upgrade gnutls to version or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* libssh2/libssh2@1.8.2-r0

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server.

Remediation

Upgrade libssh2 to version or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* libssh2/libssh2@1.8.2-r0

Overview

The SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* libssh2/libssh2@1.8.2-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. In libssh2 before 1.9.0, kex_method_diffie_hellman_group_exchange_sha256_key_exchange in kex.c has an integer overflow that could lead to an out-of-bounds read in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server. This is related to an _libssh2_check_length mistake, and is different from the various issues fixed in 1.8.1, such as CVE-2019-3855.

Remediation

Upgrade libssh2 to version or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* nghttp2/nghttp2-libs@1.35.1-r0

Overview

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

References

high severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.35.1-r0
  • Fixed in: 1.35.1-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* nghttp2/nghttp2-libs@1.35.1-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

Resource Exhaustion

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* nghttp2/nghttp2-libs@1.35.1-r0

Overview

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

References

high severity

Improper Authentication

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. A NULL pointer dereference was found in OpenLDAP server and was fixed in openldap 2.4.55, during a request for renaming RDNs. An unauthenticated attacker could remotely crash the slapd process by sending a specially crafted request, causing a Denial of Service.

Remediation

Upgrade openldap to version or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

Affected versions of this package are vulnerable to Resource Exhaustion. In filter.c in slapd in OpenLDAP before 2.4.50, LDAP search filters with nested boolean expressions can result in denial of service (daemon crash).

Remediation

Upgrade openldap to version or higher.

References

high severity

Cryptographic Issues

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1a-r1 and openssl/libssl1.1@1.1.1a-r1
  • Fixed in: 1.1.1b-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

Overview

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

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

high severity

Out-of-bounds Read

  • Vulnerable module: python2/python2
  • Introduced through: python2/python2@2.7.16-r1
  • Fixed in: 2.7.17-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* python2/python2@2.7.16-r1

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.

Details

XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.

Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.

For example, below is a sample XML document, containing an XML element- username.

<?xml version="1.0" encoding="ISO-8859-1"?>
   <username>John</username>
</xml>

An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE foo [
   <!ENTITY xxe SYSTEM "file:///etc/passwd" >]>
   <username>&xxe;</username>
</xml>

Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.

Remediation

Upgrade python2 to version or higher.

References

high severity

CVE-2019-19244

  • Vulnerable module: sqlite/sqlite-libs
  • Introduced through: sqlite/sqlite-libs@3.28.0-r0
  • Fixed in: 3.28.0-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* sqlite/sqlite-libs@3.28.0-r0

Overview

Affected versions of this package are vulnerable to CVE-2019-19244 sqlite3Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage.

Remediation

Upgrade sqlite to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: sqlite/sqlite-libs
  • Introduced through: sqlite/sqlite-libs@3.28.0-r0
  • Fixed in: 3.28.0-r3

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* sqlite/sqlite-libs@3.28.0-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.

Remediation

Upgrade sqlite to version or higher.

References

medium severity

Race Condition

  • Vulnerable module: libgcrypt/libgcrypt
  • Introduced through: libgcrypt/libgcrypt@1.8.4-r1
  • Fixed in: 1.8.5-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* libgcrypt/libgcrypt@1.8.4-r1

Overview

It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/libc6-compat
  • Introduced through: musl/libc6-compat@1.1.20-r5, musl/musl@1.1.20-r5 and others
  • Fixed in: 1.1.20-r6

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* musl/libc6-compat@1.1.20-r5
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* musl/musl@1.1.20-r5
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* musl/musl-utils@1.1.20-r5

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

Improper Authentication

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

An issue was discovered in the server in OpenLDAP before 2.4.48. When the server administrator delegates rootDN (database admin) privileges for certain databases but wants to maintain isolation (e.g., for multi-tenant deployments), slapd does not properly stop a rootDN from requesting authorization as an identity from another database during a SASL bind or with a proxyAuthz (RFC 4370) control. (It is not a common configuration to deploy a system where the server administrator and a DB administrator enjoy different levels of trust.)

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

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.1a-r1 and openssl/libssl1.1@1.1.1a-r1
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

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

Use of Insufficiently Random Values

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

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

medium severity

Arbitrary Code Injection

  • Vulnerable module: python2/python2
  • Introduced through: python2/python2@2.7.16-r1
  • Fixed in: 2.7.18-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* python2/python2@2.7.16-r1

Overview

Affected versions of this package are vulnerable to Arbitrary Code Injection. An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.)

Remediation

Upgrade python2 to version or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: sqlite/sqlite-libs
  • Introduced through: sqlite/sqlite-libs@3.28.0-r0
  • Fixed in: 3.28.0-r1

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* sqlite/sqlite-libs@3.28.0-r0

Overview

In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite/sqlite-libs
  • Introduced through: sqlite/sqlite-libs@3.28.0-r0
  • Fixed in: 3.28.0-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* sqlite/sqlite-libs@3.28.0-r0

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade sqlite to version or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* git/git@2.20.1-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

CVE-2020-25709

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

Affected versions of this package are vulnerable to CVE-2020-25709. None

Remediation

Upgrade openldap to version or higher.

low severity

CVE-2020-25710

  • Vulnerable module: openldap/libldap
  • Introduced through: openldap/libldap@2.4.47-r2
  • Fixed in: 2.4.48-r2

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openldap/libldap@2.4.47-r2

Overview

Affected versions of this package are vulnerable to CVE-2020-25710. None

Remediation

Upgrade openldap to version or higher.

low severity

Missing Encryption of Sensitive Data

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

Detailed paths

  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libcrypto1.1@1.1.1a-r1
  • Introduced through: google/cloud-sdk:258.0.0-alpine@* openssl/libssl1.1@1.1.1a-r1

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