Docker google/cloud-sdk:277.0.0-alpine

Vulnerabilities

29 via 41 paths

Dependencies

60

Source

Group 6 Copy Created with Sketch. Docker

Target OS

alpine:3.11.3
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 20
  • 7
  • 2
Status
  • 29
  • 0
  • 0

high severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/curl@7.67.0-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/libcurl@7.67.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/curl
  • Introduced through: curl/curl@7.67.0-r0 and curl/libcurl@7.67.0-r0
  • Fixed in: 7.67.0-r3

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/curl@7.67.0-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/libcurl@7.67.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/curl
  • Introduced through: curl/curl@7.67.0-r0 and curl/libcurl@7.67.0-r0
  • Fixed in: 7.67.0-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/curl@7.67.0-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/libcurl@7.67.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/curl
  • Introduced through: curl/curl@7.67.0-r0 and curl/libcurl@7.67.0-r0
  • Fixed in: 7.67.0-r3

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/curl@7.67.0-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/libcurl@7.67.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/curl
  • Introduced through: curl/curl@7.67.0-r0 and curl/libcurl@7.67.0-r0
  • Fixed in: 7.67.0-r2

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/curl@7.67.0-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* curl/libcurl@7.67.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

Insufficiently Protected Credentials

  • Vulnerable module: git/git
  • Introduced through: git/git@2.24.1-r0
  • Fixed in: 2.24.2-r0

Detailed paths

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

Out-of-bounds Write

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* gnutls/gnutls@3.6.10-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.10-r0
  • Fixed in: 3.6.14-r0

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* gnutls/gnutls@3.6.10-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.10-r0
  • Fixed in: 3.6.10-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* gnutls/gnutls@3.6.10-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

Improper Enforcement of Message or Data Structure

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

Detailed paths

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

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openldap/libldap@2.4.48-r1

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.48-r1
  • Fixed in: 2.4.48-r2

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openldap/libldap@2.4.48-r1

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
new

Inadequate Encryption Strength

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libcrypto1.1@1.1.1d-r3
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libssl1.1@1.1.1d-r3

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libcrypto1.1@1.1.1d-r3
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libssl1.1@1.1.1d-r3

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libcrypto1.1@1.1.1d-r3
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libssl1.1@1.1.1d-r3

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libcrypto1.1@1.1.1d-r3
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libssl1.1@1.1.1d-r3

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

Integer Overflow or Wraparound

  • Vulnerable module: p11-kit/p11-kit
  • Introduced through: p11-kit/p11-kit@0.23.18.1-r0
  • Fixed in: 0.23.18.1-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* p11-kit/p11-kit@0.23.18.1-r0

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.

Remediation

Upgrade p11-kit to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: p11-kit/p11-kit
  • Introduced through: p11-kit/p11-kit@0.23.18.1-r0
  • Fixed in: 0.23.18.1-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* p11-kit/p11-kit@0.23.18.1-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. An issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.

Remediation

Upgrade p11-kit to version or higher.

References

high severity
new

Buffer Overflow

  • Vulnerable module: python3/python3
  • Introduced through: python3/python3@3.8.1-r0
  • Fixed in: 3.8.2-r2

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* python3/python3@3.8.1-r0

Overview

Affected versions of this package are vulnerable to Buffer Overflow. Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callproc.c, which may lead to remote code execution in certain Python applications that accept floating-point numbers as untrusted input, as demonstrated by a 1e300 argument to c_double.from_param. This occurs because sprintf is used unsafely.

Remediation

Upgrade python3 to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: sqlite/sqlite-libs
  • Introduced through: sqlite/sqlite-libs@3.30.1-r1
  • Fixed in: 3.30.1-r2

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* sqlite/sqlite-libs@3.30.1-r1

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

Information Exposure

  • Vulnerable module: glib/glib
  • Introduced through: glib/glib@2.62.4-r0
  • Fixed in: 2.62.5-r0

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* glib/glib@2.62.4-r0

Overview

Affected versions of this package are vulnerable to Information Exposure. GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly to a target address instead of connecting via a proxy server when configured to do so, because the proxy_addr field is mishandled. This bug is timing-dependent and may occur only sporadically depending on network delays. The greatest security relevance is in use cases where a proxy is used to help with privacy/anonymity, even though there is no technical barrier to a direct connection. NOTE: versions before 2.60 are unaffected.

Remediation

Upgrade glib to version or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/libc6-compat
  • Introduced through: musl/libc6-compat@1.1.24-r0, musl/musl@1.1.24-r0 and others
  • Fixed in: 1.1.24-r3

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* musl/libc6-compat@1.1.24-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* musl/musl@1.1.24-r0
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* musl/musl-utils@1.1.24-r0

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

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libcrypto1.1@1.1.1d-r3
  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openssl/libssl1.1@1.1.1d-r3

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

Out-of-bounds Read

  • Vulnerable module: p11-kit/p11-kit
  • Introduced through: p11-kit/p11-kit@0.23.18.1-r0
  • Fixed in: 0.23.18.1-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* p11-kit/p11-kit@0.23.18.1-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.

Remediation

Upgrade p11-kit to version or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: python3/python3
  • Introduced through: python3/python3@3.8.1-r0
  • Fixed in: 3.8.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* python3/python3@3.8.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. In Python (CPython) 3.6 through 3.6.10, 3.7 through 3.7.6, and 3.8 through 3.8.1, an insecure dependency load upon launch on Windows 7 may result in an attacker's copy of api-ms-win-core-path-l1-1-0.dll being loaded and used instead of the system's copy. Windows 8 and later are unaffected.

Remediation

Upgrade python3 to version or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python3/python3
  • Introduced through: python3/python3@3.8.1-r0
  • Fixed in: 3.8.2-r0

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* python3/python3@3.8.1-r0

Overview

Affected versions of this package are vulnerable to Resource Exhaustion. Python 2.7 through 2.7.17, 3.5 through 3.5.9, 3.6 through 3.6.10, 3.7 through 3.7.6, and 3.8 through 3.8.1 allows an HTTP server to conduct Regular Expression Denial of Service (ReDoS) attacks against a client because of urllib.request.AbstractBasicAuthHandler catastrophic backtracking.

Remediation

Upgrade python3 to version or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python3/python3
  • Introduced through: python3/python3@3.8.1-r0
  • Fixed in: 3.8.2-r1

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* python3/python3@3.8.1-r0

Overview

Affected versions of this package are vulnerable to Resource Exhaustion. Lib/ipaddress.py in Python through 3.8.3 improperly computes hash values in the IPv4Interface and IPv6Interface classes, which might allow a remote attacker to cause a denial of service if an application is affected by the performance of a dictionary containing IPv4Interface or IPv6Interface objects, and this attacker can cause many dictionary entries to be created.

Remediation

Upgrade python3 to version or higher.

References

low severity

CVE-2020-25709

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

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openldap/libldap@2.4.48-r1

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.48-r1
  • Fixed in: 2.4.48-r3

Detailed paths

  • Introduced through: google/cloud-sdk:277.0.0-alpine@* openldap/libldap@2.4.48-r1

Overview

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

Remediation

Upgrade openldap to version or higher.