Vulnerabilities

427 via 1370 paths

Dependencies

282

Source

Group 6 Copy Created with Sketch. Docker

Target OS

ubuntu:18.04
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 12
  • 283
  • 132
Status
  • 427
  • 0
  • 0

high severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

high severity

Improper Encoding or Escaping of Output

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as checks for whether a UTF-8 character is valid in a certain context.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.3.5-2
  • Fixed in: 1.3.5-2ubuntu0.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libksba/libksba8@1.3.5-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libksba package and not the libksba package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found in the Libksba library due to an integer overflow within the CRL parser. The vulnerability can be exploited remotely for code execution on the target system by passing specially crafted data to the application, for example, a malicious S/MIME attachment.

Remediation

Upgrade Ubuntu:18.04 libksba to version 1.3.5-2ubuntu0.18.04.1 or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.13 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.1 or higher.

References

high severity

SQL Injection

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3ubuntu2 and cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3ubuntu2
  • Fixed in: 2.1.27~101-g0780600+dfsg-3ubuntu2.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream cyrus-sasl2 package and not the cyrus-sasl2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Cyrus SASL 2.1.17 through 2.1.27 before 2.1.28, plugins/sql.c does not escape the password for a SQL INSERT or UPDATE statement.

Remediation

Upgrade Ubuntu:18.04 cyrus-sasl2 to version 2.1.27~101-g0780600+dfsg-3ubuntu2.4 or higher.

References

high severity

CVE-2023-44487

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.30.0-1ubuntu1
  • Fixed in: 1.30.0-1ubuntu1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nghttp2/libnghttp2-14@1.30.0-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

Upgrade Ubuntu:18.04 nghttp2 to version 1.30.0-1ubuntu1+esm2 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.15

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.15 or higher.

References

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.21

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.21 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.7 or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.9 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.49

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.49 or higher.

References

medium severity

Security Features

  • Vulnerable module: apparmor/libapparmor1
  • Introduced through: apparmor/libapparmor1@2.12-4ubuntu5.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apparmor/libapparmor1@2.12-4ubuntu5.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream apparmor package and not the apparmor package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In all versions of AppArmor mount rules are accidentally widened when compiled.

Remediation

There is no fixed version for Ubuntu:18.04 apparmor.

References

medium severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.21

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously was used to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.21 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.19.0.5ubuntu2.3, dpkg/dpkg-dev@1.19.0.5ubuntu2.3 and others
  • Fixed in: 1.19.0.5ubuntu2.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dpkg@1.19.0.5ubuntu2.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dpkg/dpkg-dev@1.19.0.5ubuntu2.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dpkg/libdpkg-perl@1.19.0.5ubuntu2.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs.

Remediation

Upgrade Ubuntu:18.04 dpkg to version 1.19.0.5ubuntu2.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.7 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.9+esm1 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.9+esm1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.2 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.15

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is distributed revision control system. git log can display commits in an arbitrary format using its --format specifiers. This functionality is also exposed to git archive via the export-subst gitattribute. When processing the padding operators, there is a integer overflow in pretty.c::format_and_pad_commit() where a size_t is stored improperly as an int, and then added as an offset to a memcpy(). This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., git log --format=...). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable git archive in untrusted repositories. If you expose git archive via git daemon, disable it by running git config --global daemon.uploadArch false.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.15 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.15

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a .gitattributes file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted .gitattributes file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.15 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

stdlib/canonicalize.c in the GNU C Library (aka glibc or libc6) 2.27 and earlier, when processing very long pathname arguments to the realpath function, could encounter an integer overflow on 32-bit architectures, leading to a stack-based buffer overflow and, potentially, arbitrary code execution.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

medium severity

CVE-2022-44640

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heimdal before 7.7.1 allows remote attackers to execute arbitrary code because of an invalid free in the ASN.1 codec used by the Key Distribution Center (KDC).

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.3 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libksba/libksba8
  • Introduced through: libksba/libksba8@1.3.5-2
  • Fixed in: 1.3.5-2ubuntu0.18.04.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libksba/libksba8@1.3.5-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libksba package and not the libksba package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser.

Remediation

Upgrade Ubuntu:18.04 libksba to version 1.3.5-2ubuntu0.18.04.2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@0.0~r131-2ubuntu3
  • Fixed in: 0.0~r131-2ubuntu3.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter lz4/liblz4-1@0.0~r131-2ubuntu3

NVD Description

Note: Versions mentioned in the description apply only to the upstream lz4 package and not the lz4 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There's a flaw in lz4. An attacker who submits a crafted file to an application linked with lz4 may be able to trigger an integer overflow, leading to calling of memmove() on a negative size argument, causing an out-of-bounds write and/or a crash. The greatest impact of this flaw is to availability, with some potential impact to confidentiality and integrity as well.

Remediation

Upgrade Ubuntu:18.04 lz4 to version 0.0~r131-2ubuntu3.1 or higher.

References

medium severity

SQL Injection

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.11

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.11 or higher.

References

medium severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.17

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.17 or higher.

References

medium severity

OS Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.19

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.19 or higher.

References

medium severity

Buffer Overflow

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.10

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Keccak XKCP SHA-3 reference implementation before fdc6fef has an integer overflow and resultant buffer overflow that allows attackers to execute arbitrary code or eliminate expected cryptographic properties. This occurs in the sponge function interface.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.10 or higher.

References

medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An XML External Entity (XXE) issue was discovered in Python through 3.9.1. The plistlib module no longer accepts entity declarations in XML plist files to avoid XML vulnerabilities.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm2 or higher.

References

medium severity

Use After Free

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.56

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.56 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: zeromq3/libzmq3-dev
  • Introduced through: zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2 and zeromq3/libzmq5@4.2.5-1ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq5@4.2.5-1ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zeromq3 package and not the zeromq3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in the ZeroMQ server in versions before 4.3.3. This flaw allows a malicious client to cause a stack buffer overflow on the server by sending crafted topic subscription requests and then unsubscribing. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

There is no fixed version for Ubuntu:18.04 zeromq3.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-0ubuntu2 and zlib/zlib1g-dev@1:1.2.11.dfsg-0ubuntu2
  • Fixed in: 1:1.2.11.dfsg-0ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zlib/zlib1g@1:1.2.11.dfsg-0ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zlib/zlib1g-dev@1:1.2.11.dfsg-0ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Remediation

Upgrade Ubuntu:18.04 zlib to version 1:1.2.11.dfsg-0ubuntu2.2 or higher.

References

medium severity

CVE-2024-37371

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4+esm2 or higher.

References

medium severity

Interpretation Conflict

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1ubuntu2.2
  • Fixed in: 1.19.4-1ubuntu2.2+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter wget@1.19.4-1ubuntu2.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.

Remediation

Upgrade Ubuntu:18.04 wget to version 1.19.4-1ubuntu2.2+esm1 or higher.

References

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm1 or higher.

References

medium severity

Improper Validation of Integrity Check Value

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4+esm3 or higher.

References

medium severity

CVE-2020-19726

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in binutils libbfd.c 2.36 relating to the auxiliary symbol data allows attackers to read or write to system memory or cause a denial of service.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.13 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: gzip
  • Introduced through: gzip@1.6-5ubuntu1
  • Fixed in: 1.6-5ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gzip@1.6-5ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Ubuntu:18.04 gzip to version 1.6-5ubuntu1.2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in the HDF HDF5 1.10.4 library. There is an out of bounds read in the function H5VM_memcpyvv in H5VM.c when called from H5D__compact_readvv in H5Dcompact.c.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in the HDF HDF5 1.10.4 library. There is an out of bounds read in the function H5MM_xstrdup in H5MM.c when called from H5O_dtype_decode_helper in H5Odtype.c.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In HDF5 1.10.1, there is an out of bounds write vulnerability in the function H5G__ent_decode_vec in H5Gcache.c in libhdf5.a. For example, h5dump would crash or possibly have unspecified other impact someone opens a crafted hdf5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.3 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.3 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: python-setuptools/python3-pkg-resources
  • Introduced through: python-setuptools/python3-pkg-resources@39.0.1-2 and python-setuptools/python3-setuptools@39.0.1-2
  • Fixed in: 39.0.1-2ubuntu0.1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-pkg-resources@39.0.1-2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-setuptools@39.0.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-setuptools package and not the python-setuptools package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. A path traversal vulnerability in PackageIndex is present in setuptools prior to version 78.1.1. An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to remote code execution depending on the context. Version 78.1.1 fixes the issue.

Remediation

Upgrade Ubuntu:18.04 python-setuptools to version 39.0.1-2ubuntu0.1+esm2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Out of bounds write in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: xz-utils
  • Introduced through: xz-utils@5.2.2-1.3 and xz-utils/liblzma5@5.2.2-1.3
  • Fixed in: 5.2.2-1.3ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter xz-utils@5.2.2-1.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter xz-utils/liblzma5@5.2.2-1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Ubuntu:18.04 xz-utils to version 5.2.2-1.3ubuntu0.1 or higher.

References

medium severity

Missing Authentication for Critical Function

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.17

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.17 or higher.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.8 or higher.

References

medium severity

CVE-2025-27363

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.2+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.2+esm1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An out of bounds read was discovered in H5O_fill_new_decode and H5O_fill_old_decode in H5Ofill.c in the HDF HDF5 1.10.2 library. It could allow a remote denial of service or information disclosure attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.4-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libhogweed4@3.4-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libnettle6@3.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nettle package and not the nettle package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Nettle in versions before 3.7.2, where several Nettle signature verification functions (GOST DSA, EDDSA & ECDSA) result in the Elliptic Curve Cryptography point (ECC) multiply function being called with out-of-range scalers, possibly resulting in incorrect results. This flaw allows an attacker to force an invalid signature, causing an assertion failure or possible validation. The highest threat to this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Ubuntu:18.04 nettle to version 3.4-1ubuntu0.1 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-6ubuntu0.3, perl/libperl5.26@5.26.1-6ubuntu0.3 and others
  • Fixed in: 5.26.1-6ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/libperl5.26@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-base@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-modules-5.26@5.26.1-6ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.

Remediation

Upgrade Ubuntu:18.04 perl to version 5.26.1-6ubuntu0.7 or higher.

References

medium severity

CVE-2023-43804

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.8+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

urllib3 is a user-friendly HTTP client library for Python. urllib3 doesn't treat the Cookie HTTP header special or provide any helpers for managing cookies over HTTP, that is the responsibility of the user. However, it is possible for a user to specify a Cookie header and unknowingly leak information via HTTP redirects to a different origin if that user doesn't disable redirects explicitly. This issue has been patched in urllib3 version 1.26.17 or 2.0.5.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.8+esm2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: zeromq3/libzmq3-dev
  • Introduced through: zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2 and zeromq3/libzmq5@4.2.5-1ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq5@4.2.5-1ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zeromq3 package and not the zeromq3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There's a flaw in the zeromq server in versions before 4.3.3 in src/decoder_allocators.hpp. The decoder static allocator could have its sized changed, but the buffer would remain the same as it is a static buffer. A remote, unauthenticated attacker who sends a crafted request to the zeromq server could trigger a buffer overflow WRITE of arbitrary data if CURVE/ZAP authentication is not enabled. The greatest impact of this flaw is to application availability, data integrity, and confidentiality.

Remediation

There is no fixed version for Ubuntu:18.04 zeromq3.

References

medium severity

CVE-2022-47695

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function bfd_mach_o_get_synthetic_symtab in match-o.c.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

CVE-2022-47696

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function compare_symbols.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out of bound reads which may cause a denial of service or other unspecified impacts.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heap buffer overflow vulnerability in binutils readelf before 2.40 via function display_debug_section in file readelf.c.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heap buffer overflow vulnerability in binutils readelf before 2.40 via function find_section_in_set in file readelf.c.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.1-1ubuntu1.2, e2fsprogs/libcom-err2@1.44.1-1ubuntu1.2 and others
  • Fixed in: 1.44.1-1ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libcom-err2@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libext2fs2@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libss2@1.44.1-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream e2fsprogs package and not the e2fsprogs package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem.

Remediation

Upgrade Ubuntu:18.04 e2fsprogs to version 1.44.1-1ubuntu1.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for m_groupSize.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.2 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18 or higher.

References

medium severity

Improper Ownership Management

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.12

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.12 or higher.

References

medium severity

Uncontrolled Search Path Element

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.11

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users working on multi-user machines, where untrusted parties have write access to the same hard disk. Those untrusted parties could create the folder C:\.git, which would be picked up by Git operations run supposedly outside a repository while searching for a Git directory. Git would then respect any config in said Git directory. Git Bash users who set GIT_PS1_SHOWDIRTYSTATE are vulnerable as well. Users who installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are vulnerable: simply creating a new project would already read and respect the config specified in C:\.git\config. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder .git on all drives where Git commands are run, and remove read/write access from those folders as a workaround. Alternatively, define or extend GIT_CEILING_DIRECTORIES to cover the parent directory of the user profile, e.g. C:\Users if the user profile is located in C:\Users\my-user-name.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.11 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in GLib. The GVariant deserialization code is vulnerable to a heap buffer overflow introduced by the fix for CVE-2023-32665. This bug does not affect any released version of GLib, but does affect GLib distributors who followed the guidance of GLib developers to backport the initial fix for CVE-2023-32665.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm3 or higher.

References

medium severity

Off-by-one Error

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in glibc. An off-by-one buffer overflow and underflow in getcwd() may lead to memory corruption when the size of the buffer is exactly 1. A local attacker who can control the input buffer and size passed to getcwd() in a setuid program could use this flaw to potentially execute arbitrary code and escalate their privileges on the system.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An AVX-512-optimized implementation of the mempcpy function in the GNU C Library (aka glibc or libc6) 2.27 and earlier may write data beyond the target buffer, leading to a buffer overflow in __mempcpy_avx512_no_vzeroupper.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1 or higher.

References

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-6ubuntu0.3, perl/libperl5.26@5.26.1-6ubuntu0.3 and others
  • Fixed in: 5.26.1-6ubuntu0.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/libperl5.26@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-base@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-modules-5.26@5.26.1-6ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

CPAN 2.28 allows Signature Verification Bypass.

Remediation

Upgrade Ubuntu:18.04 perl to version 5.26.1-6ubuntu0.6 or higher.

References

medium severity

Arbitrary Command Injection

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability has been found in the CPython venv module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This means that attacker-controlled virtual environments are able to run commands when the virtual environment is activated. Virtual environments which are not created by an attacker or which aren't activated before being used (ie "./venv/bin/python") are not affected.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm3 or higher.

References

medium severity

Use After Free

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.38

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sending specially crafted dbus messages.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.38 or higher.

References

medium severity

Improper Initialization

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Binutils before 2.34 has an uninitialized-heap vulnerability in function tic4x_print_cond (file opcodes/tic4x-dis.c) which could allow attackers to make an information leak.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability, which was classified as problematic, was found in GNU Binutils up to 2.43. This affects the function disassemble_bytes of the file binutils/objdump.c. The manipulation of the argument buf leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. The identifier of the patch is baac6c221e9d69335bf41366a1c7d87d8ab2f893. It is recommended to upgrade the affected component.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm4 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: ca-certificates
  • Introduced through: ca-certificates@20180409
  • Fixed in: 20211016ubuntu0.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ca-certificates@20180409

NVD Description

Note: Versions mentioned in the description apply only to the upstream ca-certificates package and not the ca-certificates package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.

Remediation

Upgrade Ubuntu:18.04 ca-certificates to version 20211016ubuntu0.18.04.1 or higher.

References

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.15

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.15 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.12

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.12 or higher.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.18

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.18 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.12

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.12 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3ubuntu2 and cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3ubuntu2
  • Fixed in: 2.1.27~101-g0780600+dfsg-3ubuntu2.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream cyrus-sasl2 package and not the cyrus-sasl2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 cyrus-sasl2 to version 2.1.27~101-g0780600+dfsg-3ubuntu2.1 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in copyString.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.7 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.

Remediation

There is no fixed version for Ubuntu:18.04 expat.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situations.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.8 or higher.

References

medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.9+esm1 or higher.

References

medium severity

CVE-2021-40330

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected cross-protocol requests, as demonstrated by the git://localhost:1234/%0d%0a%0d%0aGET%20/%20HTTP/1.1 substring.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.9 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.16

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.16 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18 or higher.

References

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.8 or higher.

References

medium severity

Deserialization of Untrusted Data

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in glib, where the gvariant deserialization code is vulnerable to a denial of service introduced by additional input validation added to resolve CVE-2023-29499. The offset table validation may be very slow. This bug does not affect any released version of glib but does affect glib distributors who followed the guidance of glib developers to backport the initial fix for CVE-2023-29499.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm3 or higher.

References

medium severity

Incorrect Conversion between Numeric Types

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.66.6 and 2.67.x before 2.67.3. The function g_bytes_new has an integer overflow on 64-bit platforms due to an implicit cast from 64 bits to 32 bits. The overflow could potentially lead to memory corruption.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.7 or higher.

References

medium severity

Incorrect Conversion between Numeric Types

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.66.7 and 2.67.x before 2.67.4. If g_byte_array_new_take() was called with a buffer of 4GB or more on a 64-bit platform, the length would be truncated modulo 2**32, causing unintended length truncation.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.7 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization fails to validate that the input conforms to the expected format, leading to denial of service.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm3 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.28, attempting to resolve a crafted hostname via getaddrinfo() leads to the allocation of a socket descriptor that is not closed. This is related to the if_nametoindex() function.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

medium severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1ubuntu1.1
  • Fixed in: 3.5.18-1ubuntu1.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnutls28/libgnutls30@3.5.18-1ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.

Remediation

Upgrade Ubuntu:18.04 gnutls28 to version 3.5.18-1ubuntu1.6 or higher.

References

medium severity

Improper Validation of Integrity Check Value

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result of memcmp. When these patches were backported to the heimdal-7.7.1 and heimdal-7.8.0 branches (and possibly other branches) a logic inversion sneaked in causing the validation of message integrity codes in gssapi/arcfour to be inverted.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.4 or higher.

References

medium severity

Improperly Implemented Security Check for Standard

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in samba's Heimdal KDC implementation, versions 4.8.x up to, excluding 4.8.12, 4.9.x up to, excluding 4.9.8 and 4.10.x up to, excluding 4.10.3, when used in AD DC mode. A man in the middle attacker could use this flaw to intercept the request to the KDC and replace the user name (principal) in the request with any desired user name (principal) that exists in the KDC effectively obtaining a ticket for that principal.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Heimdal Software Kerberos 5 implementation is vulnerable to a null pointer dereferance. An attacker with network access to an application that depends on the vulnerable code path can cause the application to crash.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heimdal before 7.7.1 allows attackers to cause a NULL pointer dereference in a SPNEGO acceptor via a preferred_mech_type of GSS_C_NO_OID and a nonzero initial_response value to send_accept.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.3 or higher.

References

medium severity

Off-by-one Error

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Heimdal is an implementation of ASN.1/DER, PKIX, and Kerberos. Versions prior to 7.7.1 are vulnerable to a denial of service vulnerability in Heimdal's PKI certificate validation library, affecting the KDC (via PKINIT) and kinit (via PKINIT), as well as any third-party applications using Heimdal's libhx509. Users should upgrade to Heimdal 7.7.1 or 7.8. There are no known workarounds for this issue.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.2 or higher.

References

medium severity

CVE-2024-37370

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4+esm2 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to cause a NULL pointer dereference and daemon crash. This occurs because a return value is not properly managed in a certain situation.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

MIT Kerberos 5 (aka krb5) before 1.17.2 and 1.18.x before 1.18.3 allows unbounded recursion via an ASN.1-encoded Kerberos message because the lib/krb5/asn.1/asn1_encode.c support for BER indefinite lengths lacks a recursion limit.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.2 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.4.1-0ubuntu0.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libhogweed4@3.4-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libnettle6@3.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nettle package and not the nettle package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in the way nettle's RSA decryption functions handled specially crafted ciphertext. An attacker could use this flaw to provide a manipulated ciphertext leading to application crash and denial of service.

Remediation

Upgrade Ubuntu:18.04 nettle to version 3.4.1-0ubuntu0.18.04.1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.30.0-1ubuntu1
  • Fixed in: 1.30.0-1ubuntu1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nghttp2/libnghttp2-14@1.30.0-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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.

Remediation

Upgrade Ubuntu:18.04 nghttp2 to version 1.30.0-1ubuntu1+esm2 or higher.

References

medium severity

CVE-2019-9513

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.30.0-1ubuntu1
  • Fixed in: 1.30.0-1ubuntu1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nghttp2/libnghttp2-14@1.30.0-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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.

Remediation

Upgrade Ubuntu:18.04 nghttp2 to version 1.30.0-1ubuntu1+esm2 or higher.

References

medium severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.30.0-1ubuntu1
  • Fixed in: 1.30.0-1ubuntu1+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nghttp2/libnghttp2-14@1.30.0-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 nghttp2 to version 1.30.0-1ubuntu1+esm1 or higher.

References

medium severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

CVE-2020-36226

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Double Free

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Integer Underflow

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Integer Underflow

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.7 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in OpenLDAP in versions before 2.4.56. This flaw allows an attacker who sends a malicious packet processed by OpenLDAP to force a failed assertion in csnNormalize23(). The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.8 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in OpenLDAP. This flaw allows an attacker who can send a malicious packet to be processed by OpenLDAP’s slapd server, to trigger an assertion failure. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.8 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.10

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.10 or higher.

References

medium severity

Release of Invalid Pointer or Reference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.9 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.5 or higher.

References

medium severity

Double Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.21

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.

The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.

These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.

The OpenSSL asn1parse command line application is also impacted by this issue.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.21 or higher.

References

medium severity

Use After Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.21

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.

This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.21 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.9-2
  • Fixed in: 0.23.9-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter p11-kit/libp11-kit0@0.23.9-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 p11-kit to version 0.23.9-2ubuntu0.1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.9-2
  • Fixed in: 0.23.9-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter p11-kit/libp11-kit0@0.23.9-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 p11-kit to version 0.23.9-2ubuntu0.1 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: python-cryptography/python3-cryptography
  • Introduced through: python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3
  • Fixed in: 2.1.4-1ubuntu1.4+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-cryptography package and not the python-cryptography package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

Remediation

Upgrade Ubuntu:18.04 python-cryptography to version 2.1.4-1ubuntu1.4+esm1 or higher.

References

medium severity

CVE-2024-3651

  • Vulnerable module: python-idna/python3-idna
  • Introduced through: python-idna/python3-idna@2.6-1
  • Fixed in: 2.6-1ubuntu0.1~esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-idna/python3-idna@2.6-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-idna package and not the python-idna package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was identified in the kjd/idna library, specifically within the idna.encode() function, affecting version 3.6. The issue arises from the function's handling of crafted input strings, which can lead to quadratic complexity and consequently, a denial of service condition. This vulnerability is triggered by a crafted input that causes the idna.encode() function to process the input with considerable computational load, significantly increasing the processing time in a quadratic manner relative to the input size.

Remediation

Upgrade Ubuntu:18.04 python-idna to version 2.6-1ubuntu0.1~esm1 or higher.

References

medium severity

CVE-2022-40898

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue discovered in Python Packaging Authority (PyPA) Wheel 0.37.1 and earlier allows remote attackers to cause a denial of service via attacker controlled input to wheel cli.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.7 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.4 or higher.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.2 or higher.

References

medium severity

Algorithmic Complexity

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.9 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Python, specifically within the urllib.parse module. This module helps break Uniform Resource Locator (URL) strings into components. The issue involves how the urlparse method does not sanitize input and allows characters like '\r' and '\n' in the URL path. This flaw allows an attacker to input a crafted URL, leading to injection attacks. This flaw affects Python versions prior to 3.10.0b1, 3.9.5, 3.8.11, 3.7.11 and 3.6.14.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.7 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Lib/tarfile.py in Python through 3.8.3, an attacker is able to craft a TAR archive leading to an infinite loop when opened by tarfile.open, because _proc_pax lacks header validation.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.1 or higher.

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There is a MEDIUM severity vulnerability affecting CPython.

Regular expressions that allowed excessive backtracking during tarfile.TarFile header parsing are vulnerable to ReDoS via specifically-crafted tar archives.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm3 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.6 or higher.

References

medium severity

Use After Free

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use-after-free exists in Python through 3.9 via heappushpop in heapq.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm2 or higher.

References

medium severity

CVE-2019-19959

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for example) valgrind.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Improper Validation of Array Index

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.7 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In SQlite 3.31.1, a potential null pointer derreference was found in the INTERSEC query processing.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.6 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

multiSelect in select.c in SQLite 3.30.1 mishandles certain errors during parsing, as demonstrated by errors from sqlite3WindowRewrite() calls. NOTE: this vulnerability exists because of an incomplete fix for CVE-2019-19880.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results).

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated column optimizations.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Unrestricted Upload of File with Dangerous Type

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

CVE-2022-40898

  • Vulnerable module: wheel/python3-wheel
  • Introduced through: wheel/python3-wheel@0.30.0-0.2
  • Fixed in: 0.30.0-0.2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter wheel/python3-wheel@0.30.0-0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream wheel package and not the wheel package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue discovered in Python Packaging Authority (PyPA) Wheel 0.37.1 and earlier allows remote attackers to cause a denial of service via attacker controlled input to wheel cli.

Remediation

Upgrade Ubuntu:18.04 wheel to version 0.30.0-0.2ubuntu0.1 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: zeromq3/libzmq3-dev
  • Introduced through: zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2 and zeromq3/libzmq5@4.2.5-1ubuntu0.2
  • Fixed in: 4.2.5-1ubuntu0.2+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq3-dev@4.2.5-1ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zeromq3/libzmq5@4.2.5-1ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zeromq3 package and not the zeromq3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In ZeroMQ before version 4.3.3, there is a denial-of-service vulnerability. Users with TCP transport public endpoints, even with CURVE/ZAP enabled, are impacted. If a raw TCP socket is opened and connected to an endpoint that is fully configured with CURVE/ZAP, legitimate clients will not be able to exchange any message. Handshakes complete successfully, and messages are delivered to the library, but the server application never receives them. This is patched in version 4.3.3.

Remediation

Upgrade Ubuntu:18.04 zeromq3 to version 4.2.5-1ubuntu0.2+esm1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-0ubuntu2 and zlib/zlib1g-dev@1:1.2.11.dfsg-0ubuntu2
  • Fixed in: 1:1.2.11.dfsg-0ubuntu2.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zlib/zlib1g@1:1.2.11.dfsg-0ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter zlib/zlib1g-dev@1:1.2.11.dfsg-0ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Ubuntu:18.04 zlib to version 1:1.2.11.dfsg-0ubuntu2.1 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.13 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.7+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.7+esm1 or higher.

References

medium severity

Improper Encoding or Escaping of Output

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

http.client in Python 3.x before 3.5.10, 3.6.x before 3.6.12, 3.7.x before 3.7.9, and 3.8.x before 3.8.5 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of HTTPConnection.request.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.3 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An out-of-bounds read flaw was found in the parse_module function in bfd/vms-alpha.c in Binutils.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

medium severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.4 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.1-1ubuntu1.2, e2fsprogs/libcom-err2@1.44.1-1ubuntu1.2 and others
  • Fixed in: 1.44.1-1ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libcom-err2@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libext2fs2@1.44.1-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter e2fsprogs/libss2@1.44.1-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream e2fsprogs package and not the e2fsprogs package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

Remediation

Upgrade Ubuntu:18.04 e2fsprogs to version 1.44.1-1ubuntu1.3 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.19

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.19 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.23

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.23 or higher.

References

medium severity

CVE-2023-46218

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.

It could do this by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with domain=co.UK when the URL used a lower case hostname curl.co.uk, even though co.uk is listed as a PSL domain.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm3 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libcurl's ASN1 parser code has the GTime2str() function, used for parsing an ASN.1 Generalized Time field. If given an syntactically incorrect field, the parser might end up using -1 for the length of the time fraction, leading to a strlen() getting performed on a pointer to a heap buffer area that is not (purposely) null terminated.

This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm5 or higher.

References

medium severity

CVE-2022-42012

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.2-1ubuntu1.2 and dbus/libdbus-1-3@1.12.2-1ubuntu1.2
  • Fixed in: 1.12.2-1ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus@1.12.2-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus/libdbus-1-3@1.12.2-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash by sending a message with attached file descriptors in an unexpected format.

Remediation

Upgrade Ubuntu:18.04 dbus to version 1.12.2-1ubuntu1.4 or higher.

References

medium severity

Improper Validation of Array Index

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.2-1ubuntu1.2 and dbus/libdbus-1-3@1.12.2-1ubuntu1.2
  • Fixed in: 1.12.2-1ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus@1.12.2-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus/libdbus-1-3@1.12.2-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message where an array length is inconsistent with the size of the element type.

Remediation

Upgrade Ubuntu:18.04 dbus to version 1.12.2-1ubuntu1.4 or higher.

References

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.2-1ubuntu1.2 and dbus/libdbus-1-3@1.12.2-1ubuntu1.2
  • Fixed in: 1.12.2-1ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus@1.12.2-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus/libdbus-1-3@1.12.2-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in D-Bus before 1.12.24, 1.13.x and 1.14.x before 1.14.4, and 1.15.x before 1.15.2. An authenticated attacker can cause dbus-daemon and other programs that use libdbus to crash when receiving a message with certain invalid type signatures.

Remediation

Upgrade Ubuntu:18.04 dbus to version 1.12.2-1ubuntu1.4 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.5, an attacker can trigger stack exhaustion in build_model via a large nesting depth in the DTD element.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.7 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: gnupg2
  • Introduced through: gnupg2@2.2.4-1ubuntu1.2, gnupg2/dirmngr@2.2.4-1ubuntu1.2 and others
  • Fixed in: 2.2.4-1ubuntu1.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/dirmngr@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-l10n@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-utils@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-agent@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-client@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-server@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgconf@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgsm@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgv@2.2.4-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.

Remediation

Upgrade Ubuntu:18.04 gnupg2 to version 2.2.4-1ubuntu1.6 or higher.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A division by zero was discovered in H5D__chunk_init in H5Dchunk.c in the HDF HDF5 1.10.2 library. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In HDF5 1.10.1, there is a divide-by-zero vulnerability in the function H5T_set_loc in the H5T.c file in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A SIGFPE signal is raised in the function apply_filters() of h5repack_filters.c in the HDF HDF5 through 1.10.3 library during an attempted parse of a crafted HDF file, because of incorrect protection against division by zero. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A SIGFPE signal is raised in the function H5D__select_io() of H5Dselect.c in the HDF HDF5 through 1.10.3 library during an attempted parse of a crafted HDF file, because of incorrect protection against division by zero. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A SIGFPE signal is raised in the function H5D__create_chunk_file_map_hyper() of H5Dchunk.c in the HDF HDF5 through 1.10.3 library during an attempted parse of a crafted HDF file, because of incorrect protection against division by zero. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Divide By Zero

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A division by zero was discovered in H5D__btree_decode_key in H5Dbtree.c in the HDF HDF5 1.10.2 library. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Memory leak in the H5O__chunk_deserialize() function in H5Ocache.c in the HDF HDF5 through 1.10.3 library allows attackers to cause a denial of service (memory consumption) via a crafted HDF5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Memory leak in the H5O_dtype_decode_helper() function in H5Odtype.c in the HDF HDF5 through 1.10.3 library allows attackers to cause a denial of service (memory consumption) via a crafted HDF5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In HDF5 1.10.1, there is a NULL pointer dereference in the function H5O_pline_decode in the H5Opline.c file in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A NULL pointer dereference in H5O_sdspace_encode() in H5Osdspace.c in the HDF HDF5 through 1.10.3 library allows attackers to cause a denial of service via a crafted HDF5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A NULL pointer dereference was discovered in H5O__chunk_deserialize in H5Ocache.c in the HDF HDF5 1.10.2 library. It could allow a remote denial of service attack.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In HDF5 1.10.1, there is an out of bounds read vulnerability in the function H5T_conv_struct_opt in H5Tconv.c in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In HDF5 1.10.1, there is an out of bounds read vulnerability in the function H5Opline_pline_decode in H5Opline.c in libhdf5.a. For example, h5dump would crash when someone opens a crafted hdf5 file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in the HDF HDF5 1.10.4 library. There is an out of bounds read in the function H5T_close_real in H5T.c.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: hdf5/hdf5-helpers
  • Introduced through: hdf5/hdf5-helpers@1.10.0-patch1+docs-4, hdf5/libhdf5-100@1.10.0-patch1+docs-4 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/hdf5-helpers@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-cpp-100@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-dev@1.10.0-patch1+docs-4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter hdf5/libhdf5-serial-dev@1.10.0-patch1+docs-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream hdf5 package and not the hdf5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A heap-based buffer overflow in ReadGifImageDesc() in gifread.c in the HDF HDF5 through 1.10.3 library allows attackers to cause a denial of service via a crafted HDF5 file. This issue was triggered while converting a GIF file to an HDF file.

Remediation

There is no fixed version for Ubuntu:18.04 hdf5.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A heap-based buffer overflow vulnerability was found in Samba within the GSSAPI unwrap_des() and unwrap_des3() routines of Heimdal. The DES and Triple-DES decryption routines in the Heimdal GSSAPI library allow a length-limited write buffer overflow on malloc() allocated memory when presented with a maliciously small packet. This flaw allows a remote user to send specially crafted malicious data to the application, possibly resulting in a denial of service (DoS) attack.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.3 or higher.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4+esm1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Buffer Overflow vulnerability in postprocess_terminfo function in tinfo/parse_entry.c:997 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1+esm1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.23

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.23 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.3 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client. The greatest threat that this flaw poses is to application availability.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.6 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

read_ints in plistlib.py in Python through 3.9.1 is vulnerable to a potential DoS attack via CPU and RAM exhaustion when processing malformed Apple Property List files in binary format.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm1 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Insufficient data validation in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to bypass defense-in-depth measures via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Uninitialized data in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

medium severity

Race Condition

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4ubuntu1.1
  • Fixed in: 1.8.1-4ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libgcrypt20@1.8.1-4ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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.

Remediation

Upgrade Ubuntu:18.04 libgcrypt20 to version 1.8.1-4ubuntu1.2 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

FreeType 2.8.1 has a signed integer overflow in cf2_doFlex in cff/cf2intrp.c.

Remediation

There is no fixed version for Ubuntu:18.04 freetype.

References

medium severity
new

Open Redirect

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.8+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

urllib3 before 1.24.2 does not remove the authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext. NOTE: this issue exists because of an incomplete fix for CVE-2018-20060 (which was case-sensitive).

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.8+esm2 or higher.

References

medium severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.19.4-1ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter wget@1.19.4-1ubuntu2.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

Remediation

There is no fixed version for Ubuntu:18.04 wget.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24 or higher.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.15

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.15 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.19

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.19 or higher.

References

medium severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.22

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.22 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1ubuntu1.1
  • Fixed in: 3.5.18-1ubuntu1.6+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnutls28/libgnutls30@3.5.18-1ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.

Remediation

Upgrade Ubuntu:18.04 gnutls28 to version 3.5.18-1ubuntu1.6+esm1 or higher.

References

medium severity

Reversible One-Way Hash

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.4+esm5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.4+esm5 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4ubuntu1.1
  • Fixed in: 1.8.1-4ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libgcrypt20@1.8.1-4ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.

Remediation

Upgrade Ubuntu:18.04 libgcrypt20 to version 1.8.1-4ubuntu1.3 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.21

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.21 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. 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 Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.8 or higher.

References

medium severity

Covert Timing Channel

  • Vulnerable module: python-cryptography/python3-cryptography
  • Introduced through: python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3
  • Fixed in: 2.1.4-1ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-cryptography package and not the python-cryptography package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

python-cryptography 3.2 is vulnerable to Bleichenbacher timing attacks in the RSA decryption API, via timed processing of valid PKCS#1 v1.5 ciphertext.

Remediation

Upgrade Ubuntu:18.04 python-cryptography to version 2.1.4-1ubuntu1.4 or higher.

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.6 or higher.

References

medium severity

Inefficient Regular Expression Complexity

  • Vulnerable module: python-setuptools/python3-pkg-resources
  • Introduced through: python-setuptools/python3-pkg-resources@39.0.1-2 and python-setuptools/python3-setuptools@39.0.1-2
  • Fixed in: 39.0.1-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-pkg-resources@39.0.1-2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-setuptools@39.0.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-setuptools package and not the python-setuptools package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py.

Remediation

Upgrade Ubuntu:18.04 python-setuptools to version 39.0.1-2ubuntu0.1 or higher.

References

medium severity

Race Condition

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in compare_digest in Lib/hmac.py in Python through 3.9.1. Constant-time-defeating optimisations were possible in the accumulator variable in hmac.compare_digest.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm2 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: apt
  • Introduced through: apt@1.6.12, apt/libapt-inst2.0@1.6.12ubuntu0.1 and others
  • Fixed in: 1.6.12ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apt@1.6.12
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apt/libapt-inst2.0@1.6.12ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apt/libapt-pkg5.0@1.6.12

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

APT had several integer overflows and underflows while parsing .deb packages, aka GHSL-2020-168 GHSL-2020-169, in files apt-pkg/contrib/extracttar.cc, apt-pkg/deb/debfile.cc, and apt-pkg/contrib/arfile.cc. This issue affects: apt 1.2.32ubuntu0 versions prior to 1.2.32ubuntu0.2; 1.6.12ubuntu0 versions prior to 1.6.12ubuntu0.2; 2.0.2ubuntu0 versions prior to 2.0.2ubuntu0.2; 2.1.10ubuntu0 versions prior to 2.1.10ubuntu0.1;

Remediation

Upgrade Ubuntu:18.04 apt to version 1.6.12ubuntu0.2 or higher.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.17

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.17 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: apt
  • Introduced through: apt@1.6.12 and apt/libapt-pkg5.0@1.6.12
  • Fixed in: 1.6.12ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apt@1.6.12
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter apt/libapt-pkg5.0@1.6.12

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

Remediation

Upgrade Ubuntu:18.04 apt to version 1.6.12ubuntu0.1 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A memory consumption issue in get_data function in binutils/nm.c in GNU nm before 2.34 allows attackers to cause a denial of service via crafted command.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in GNU Binutils 2.34. It is a memory leak when process microblaze-dis.c. This one will consume memory on each insn disassembled.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In GNU Binutils before 2.40, there is a heap-buffer-overflow in the error function bfd_getl32 when called from the strip_main function in strip-new via a crafted file.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.8 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in Binutils readelf 2.38.50, reachable assertion failure in function display_debug_names allows attackers to cause a denial of service.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm3 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Binutils. The use of an uninitialized field in the struct module *module may lead to application crash and local denial of service.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Binutils. The field the_bfd of asymbolstruct is uninitialized in the bfd_mach_o_get_synthetic_symtab function, which may lead to an application crash and local denial of service.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: gcc-7
  • Introduced through: gcc-7@7.5.0-3ubuntu1~18.04, gcc-7/cpp-7@7.5.0-3ubuntu1~18.04 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/cpp-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/g++-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/gcc-7-base@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libasan4@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libcilkrts5@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libgcc-7-dev@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libgfortran4@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libstdc++-7-dev@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libubsan0@7.5.0-3ubuntu1~18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-7 package and not the gcc-7 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Arm Armv8-A core implementations utilizing speculative execution past unconditional changes in control flow may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka "straight-line speculation."

Remediation

There is no fixed version for Ubuntu:18.04 gcc-7.

References

medium severity

Information Exposure

  • Vulnerable module: gcc-8/gcc-8-base
  • Introduced through: gcc-8/gcc-8-base@8.4.0-1ubuntu1~18.04, gcc-8/libatomic1@8.4.0-1ubuntu1~18.04 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/gcc-8-base@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libatomic1@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libcc1-0@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libgcc1@1:8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libgomp1@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libitm1@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/liblsan0@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libmpx2@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libquadmath0@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libstdc++6@8.4.0-1ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-8/libtsan0@8.4.0-1ubuntu1~18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-8 package and not the gcc-8 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Arm Armv8-A core implementations utilizing speculative execution past unconditional changes in control flow may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka "straight-line speculation."

Remediation

There is no fixed version for Ubuntu:18.04 gcc-8.

References

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's $GIT_DIR/objects directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via --no-hardlinks). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the --recurse-submodules option. Git does not create symbolic links in the $GIT_DIR/objects directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the --local optimization when on a shared machine, either by passing the --no-local option to git clone or cloning from a URL that uses the file:// scheme. Alternatively, avoid cloning repositories from untrusted sources with --recurse-submodules or run git config --global protocol.file.allow user.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.13 or higher.

References

medium severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.16

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253.

A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with --recurse-submodules. Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.16 or higher.

References

medium severity

Deserialization of Untrusted Data

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to an exponential blowup issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm3 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in glib before version 2.63.6. Due to random charset alias, pkexec can leak content from files owned by privileged users to unprivileged ones under the right condition.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9 or higher.

References

medium severity

Resource Exhaustion

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in GLib. GVariant deserialization is vulnerable to a slowdown issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm3 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg-turbo8
  • Introduced through: libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4 and libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4
  • Fixed in: 1.5.2-0ubuntu5.18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A crafted input file could cause a null pointer dereference in jcopy_sample_rows() when processed by libjpeg-turbo.

Remediation

Upgrade Ubuntu:18.04 libjpeg-turbo to version 1.5.2-0ubuntu5.18.04.6 or higher.

References

medium severity

Incorrect Default Permissions

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.3+dfsg-2ubuntu1.1
  • Fixed in: 1.3.3+dfsg-2ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libzstd/libzstd1@1.3.3+dfsg-2ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libzstd package and not the libzstd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In the Zstandard command-line utility prior to v1.4.1, output files were created with default permissions. Correct file permissions (matching the input) would only be set at completion time. Output files could therefore be readable or writable to unintended parties.

Remediation

Upgrade Ubuntu:18.04 libzstd to version 1.3.3+dfsg-2ubuntu1.2 or higher.

References

medium severity

CVE-2024-22365

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1, pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1 and others
  • Fixed in: 1.1.8-3.6ubuntu2.18.04.6+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-runtime@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam0g@1.1.8-3.6ubuntu2.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.

Remediation

Upgrade Ubuntu:18.04 pam to version 1.1.8-3.6ubuntu2.18.04.6+esm1 or higher.

References

medium severity

CVE-2020-15709

  • Vulnerable module: software-properties/python3-software-properties
  • Introduced through: software-properties/python3-software-properties@0.96.24.32.13 and software-properties/software-properties-common@0.96.24.32.13
  • Fixed in: 0.96.24.32.14

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter software-properties/python3-software-properties@0.96.24.32.13
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter software-properties/software-properties-common@0.96.24.32.13

NVD Description

Note: Versions mentioned in the description apply only to the upstream software-properties package and not the software-properties package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Versions of add-apt-repository before 0.98.9.2, 0.96.24.32.14, 0.96.20.10, and 0.92.37.8ubuntu0.1~esm1, printed a PPA (personal package archive) description to the terminal as-is, which allowed PPA owners to provide ANSI terminal escapes to modify terminal contents in unexpected ways.

Remediation

Upgrade Ubuntu:18.04 software-properties to version 0.96.24.32.14 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.4 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.4

medium severity

Off-by-one Error

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.57

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.57 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1
  • Fixed in: 1.29b-2ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter tar@1.29b-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Remediation

Upgrade Ubuntu:18.04 tar to version 1.29b-2ubuntu0.4 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21ubuntu1
  • Fixed in: 6.0-21ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter unzip@6.0-21ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Ubuntu:18.04 unzip to version 6.0-21ubuntu1.2 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.13

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP requests, and therefore risks leaking sensitive data to the server that is the target of the second HTTP request.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.13 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.14

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

curl supports the -t command line option, known as CURLOPT_TELNETOPTIONSin libcurl. This rarely used option is used to send variable=content pairs toTELNET servers.Due to flaw in the option parser for sending NEW_ENV variables, libcurlcould be made to pass on uninitialized data from a stack based buffer to theserver. Therefore potentially revealing sensitive internal information to theserver using a clear-text network protocol.This could happen because curl did not call and use sscanf() correctly whenparsing the string provided by the application.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.14 or higher.

References

medium severity

Link Following

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.8 or higher.

References

medium severity

Reachable Assertion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others
  • Fixed in: 1.16-2ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request.

Remediation

Upgrade Ubuntu:18.04 krb5 to version 1.16-2ubuntu0.3 or higher.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.20

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.20 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.9-2
  • Fixed in: 0.23.9-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter p11-kit/libp11-kit0@0.23.9-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 p11-kit to version 0.23.9-2ubuntu0.1 or higher.

References

medium severity

CVE-2023-40217

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm1 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The email module of Python through 3.11.3 incorrectly parses e-mail addresses that contain a special character. The wrong portion of an RFC2822 header is identified as the value of the addr-spec. In some applications, an attacker can bypass a protection mechanism in which application access is granted only after verifying receipt of e-mail to a specific domain (e.g., only @company.example.com addresses may be used for signup). This occurs in email/_parseaddr.py in recent versions of Python.

Remediation

There is no fixed version for Ubuntu:18.04 python3.6.

References

medium severity

Unchecked Return Value

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Python, specifically in the FTP (File Transfer Protocol) client library in PASV (passive) mode. The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.7 or higher.

References

medium severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm4 or higher.

References

medium severity

Incorrect Default Permissions

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.3.3+dfsg-2ubuntu1.1
  • Fixed in: 1.3.3+dfsg-2ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libzstd/libzstd1@1.3.3+dfsg-2ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libzstd package and not the libzstd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Beginning in v1.4.1 and prior to v1.4.9, due to an incomplete fix for CVE-2021-24031, the Zstandard command-line utility created output files with default permissions and restricted those permissions immediately afterwards. Output files could therefore momentarily be readable or writable to unintended parties.

Remediation

Upgrade Ubuntu:18.04 libzstd to version 1.3.3+dfsg-2ubuntu1.2 or higher.

References

medium severity

Insecure Storage of Sensitive Information

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1, pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-runtime@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam0g@1.1.8-3.6ubuntu2.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

Remediation

There is no fixed version for Ubuntu:18.04 pam.

References

medium severity

CVE-2023-45803

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.8+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like POST) to GET as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren't putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn't exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that aren't expecting to respond with redirects with redirects=False and disable automatic redirects with redirects=False and handle 301, 302, and 303 redirects manually by stripping the HTTP request body.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.8+esm2 or higher.

References

medium severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.14

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths case insensitively,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.14 or higher.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: python-apt/python-apt-common
  • Introduced through: python-apt/python-apt-common@1.6.5ubuntu0.3 and python-apt/python3-apt@1.6.5ubuntu0.3
  • Fixed in: 1.6.5ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-apt/python-apt-common@1.6.5ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-apt/python3-apt@1.6.5ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-apt package and not the python-apt package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Various memory and file descriptor leaks were found in apt-python files python/arfile.cc, python/tag.cc, python/tarfile.cc, aka GHSL-2020-170. This issue affects: python-apt 1.1.0beta1 versions prior to 1.1.0beta1ubuntu0.16.04.10; 1.6.5ubuntu0 versions prior to 1.6.5ubuntu0.4; 2.0.0ubuntu0 versions prior to 2.0.0ubuntu0.20.04.2; 2.1.3ubuntu1 versions prior to 2.1.3ubuntu1.1;

Remediation

Upgrade Ubuntu:18.04 python-apt to version 1.6.5ubuntu0.4 or higher.

References

medium severity

Use of Externally-Controlled Format String

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.

This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18 or higher.

References

medium severity

CVE-2024-2398

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm4 or higher.

References

medium severity

CVE-2024-50602

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.9+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.9+esm2 or higher.

References

medium severity
new

Arbitrary Argument Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git GUI allows you to use the Git source control management tools via a GUI. When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite files for which the user has write permission. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm4 or higher.

References

medium severity
new

Buffer Overflow

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm2 or higher.

References

medium severity

CVE-2024-32004

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm1 or higher.

References

medium severity

CVE-2024-32020

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm1 or higher.

References

medium severity

CVE-2024-32021

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm1 or higher.

References

medium severity

CVE-2024-32465

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm1 or higher.

References

medium severity

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Remediation

There is no fixed version for Ubuntu:18.04 git.

References

medium severity
new

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm2 or higher.

References

medium severity
new

OS Command Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.17.1-1ubuntu0.7 and git/git-man@1:2.17.1-1ubuntu0.7
  • Fixed in: 1:2.17.1-1ubuntu0.18+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git@1:2.17.1-1ubuntu0.7
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter git/git-man@1:2.17.1-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.

Remediation

Upgrade Ubuntu:18.04 git to version 1:2.17.1-1ubuntu0.18+esm4 or higher.

References

medium severity

CVE-2024-52533

  • Vulnerable module: glib2.0/libglib2.0-0
  • Introduced through: glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6
  • Fixed in: 2.56.4-0ubuntu0.18.04.9+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glib2.0/libglib2.0-0@2.56.4-0ubuntu0.18.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CONN_MSG_LEN is not sufficient for a trailing '\0' character.

Remediation

Upgrade Ubuntu:18.04 glib2.0 to version 2.56.4-0ubuntu0.18.04.9+esm4 or higher.

References

medium severity

CVE-2024-2961

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm2 or higher.

References

medium severity

CVE-2024-33599

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nscd: Stack-based buffer overflow in netgroup cache

If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm3 or higher.

References

medium severity

CVE-2024-33600

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nscd: Null pointer crashes after notfound response

If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm3 or higher.

References

medium severity

CVE-2024-33601

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nscd: netgroup cache may terminate daemon on memory allocation failure

The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm3 or higher.

References

medium severity

CVE-2024-33602

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nscd: netgroup cache assumes NSS callback uses in-buffer strings

The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.

This vulnerability is only present in the nscd binary.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm3 or higher.

References

medium severity

CVE-2025-0395

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm4 or higher.

References

medium severity

CVE-2025-4802

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm5 or higher.

References

medium severity

CVE-2024-28182

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.30.0-1ubuntu1
  • Fixed in: 1.30.0-1ubuntu1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nghttp2/libnghttp2-14@1.30.0-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.

Remediation

Upgrade Ubuntu:18.04 nghttp2 to version 1.30.0-1ubuntu1+esm2 or higher.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.8+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability in the package_index module of pypa/setuptools versions up to 69.1.1 allows for remote code execution via its download functions. These functions, which are used to download packages from URLs provided by users or retrieved from package index servers, are susceptible to code injection. If these functions are exposed to user-controlled inputs, such as package URLs, they can execute arbitrary commands on the system. The issue is fixed in version 70.0.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.8+esm4 or higher.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Requests is a HTTP library. Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. Users should upgrade to version 2.32.4 to receive a fix. For older versions of Requests, use of the .netrc file can be disabled with trust_env=False on one's Requests Session.

Remediation

There is no fixed version for Ubuntu:18.04 python-pip.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python-setuptools/python3-pkg-resources
  • Introduced through: python-setuptools/python3-pkg-resources@39.0.1-2 and python-setuptools/python3-setuptools@39.0.1-2
  • Fixed in: 39.0.1-2ubuntu0.1+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-pkg-resources@39.0.1-2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-setuptools/python3-setuptools@39.0.1-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-setuptools package and not the python-setuptools package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability in the package_index module of pypa/setuptools versions up to 69.1.1 allows for remote code execution via its download functions. These functions, which are used to download packages from URLs provided by users or retrieved from package index servers, are susceptible to code injection. If these functions are exposed to user-controlled inputs, such as package URLs, they can execute arbitrary commands on the system. The issue is fixed in version 70.0.

Remediation

Upgrade Ubuntu:18.04 python-setuptools to version 39.0.1-2ubuntu0.1+esm1 or higher.

References

medium severity

CVE-2024-0450

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was found in the CPython zipfile module affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and prior.

The zipfile module is vulnerable to “quoted-overlap” zip-bombs which exploit the zip format to create a zip-bomb with a high compression ratio. The fixed versions of CPython makes the zipfile module reject zip archives which overlap entries in the archive.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm2 or higher.

References

medium severity

CVE-2024-11168

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The urllib.parse.urlsplit() and urlparse() functions improperly validated bracketed hosts ([]), allowing hosts that weren't IPv6 or IPvFuture. This behavior was not conformant to RFC 3986 and potentially enabled SSRF if a URL is processed by more than one URL parser.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm3 or higher.

References

medium severity

CVE-2025-0938

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Python standard library functions urllib.parse.urlsplit and urlparse accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This could result in differential parsing across the Python URL parser and other specification-compliant URL parsers.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm4 or higher.

References

medium severity

CVE-2025-4516

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There is an issue in CPython when using bytes.decode(&#34;unicode_escape&#34;, error=&#34;ignore|replace&#34;). If you are not using the "unicode_escape" encoding or an error handler your usage is not affected. To work-around this issue you may stop using the error= handler and instead wrap the bytes.decode() call in a try-except catching the DecodeError.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm5 or higher.

References

medium severity
new

CVE-2025-6069

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.

Remediation

There is no fixed version for Ubuntu:18.04 python3.6.

References

medium severity

CVE-2023-39804

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1
  • Fixed in: 1.29b-2ubuntu0.4+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter tar@1.29b-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

Remediation

Upgrade Ubuntu:18.04 tar to version 1.29b-2ubuntu0.4+esm1 or higher.

References

medium severity
new

Directory Traversal

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter tar@1.29b-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Remediation

There is no fixed version for Ubuntu:18.04 tar.

References

low severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Buffer Overflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its path argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free. It may use the notification thread attributes object (passed through its struct sigevent parameter) after it has been freed by the caller, leading to a denial of service (application crash) or possibly unspecified other impact.

Remediation

There is no fixed version for Ubuntu:18.04 glibc.

References

low severity

Improper Authentication

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1, pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1 and others
  • Fixed in: 1.1.8-3.6ubuntu2.18.04.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-modules-bin@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam-runtime@1.1.8-3.6ubuntu2.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pam/libpam0g@1.1.8-3.6ubuntu2.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The Linux-PAM package before 1.5.2-6.1 for openSUSE Tumbleweed allows authentication bypass for SSH logins. The pam_access.so module doesn't correctly restrict login if a user tries to connect from an IP address that is not resolvable via DNS. In such conditions, a user with denied access to a machine can still get access. NOTE: the relevance of this issue is largely limited to openSUSE Tumbleweed and openSUSE Factory; it does not affect Linux-PAM upstream.

Remediation

Upgrade Ubuntu:18.04 pam to version 1.1.8-3.6ubuntu2.18.04.4 or higher.

References

low severity

CVE-2020-27619

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.4 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The wordexp function in the GNU C Library (aka glibc) through 2.33 may crash or read arbitrary memory in parse_param (in posix/wordexp.c) when called with an untrusted, crafted pattern, potentially resulting in a denial of service or disclosure of information. This occurs because atoi was used but strtoul should have been used to ensure correct calculations.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24 or higher.

References

low severity

Directory Traversal

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24 or higher.

References

low severity

Incorrect Calculation

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.5-3ubuntu0.2 and expat/libexpat1-dev@2.2.5-3ubuntu0.2
  • Fixed in: 2.2.5-3ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1@2.2.5-3ubuntu0.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter expat/libexpat1-dev@2.2.5-3ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts function in xmlparse.c can lead to realloc misbehavior (e.g., allocating too few bytes, or only freeing memory).

Remediation

Upgrade Ubuntu:18.04 expat to version 2.2.5-3ubuntu0.4 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg-turbo8
  • Introduced through: libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4 and libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4
  • Fixed in: 1.5.2-0ubuntu5.18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service.

Remediation

Upgrade Ubuntu:18.04 libjpeg-turbo to version 1.5.2-0ubuntu5.18.04.6 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Integer overflow in SQLite via WebSQL in Google Chrome prior to 74.0.3729.131 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.2 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-6ubuntu0.3, perl/libperl5.26@5.26.1-6ubuntu0.3 and others
  • Fixed in: 5.26.1-6ubuntu0.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/libperl5.26@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-base@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-modules-5.26@5.26.1-6ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

Remediation

Upgrade Ubuntu:18.04 perl to version 5.26.1-6ubuntu0.5 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-6ubuntu0.3, perl/libperl5.26@5.26.1-6ubuntu0.3 and others
  • Fixed in: 5.26.1-6ubuntu0.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/libperl5.26@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-base@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-modules-5.26@5.26.1-6ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

Remediation

Upgrade Ubuntu:18.04 perl to version 5.26.1-6ubuntu0.5 or higher.

References

low severity

Information Exposure

  • Vulnerable module: gcc-7
  • Introduced through: gcc-7@7.5.0-3ubuntu1~18.04, gcc-7/cpp-7@7.5.0-3ubuntu1~18.04 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/cpp-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/g++-7@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/gcc-7-base@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libasan4@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libcilkrts5@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libgcc-7-dev@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libgfortran4@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libstdc++-7-dev@7.5.0-3ubuntu1~18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gcc-7/libubsan0@7.5.0-3ubuntu1~18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-7 package and not the gcc-7 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.

Remediation

There is no fixed version for Ubuntu:18.04 gcc-7.

References

low severity

Integer Underflow

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@4.4.18-2ubuntu1.2
  • Fixed in: 4.4.18-2ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter bash@4.4.18-2ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream bash package and not the bash package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Remediation

Upgrade Ubuntu:18.04 bash to version 4.4.18-2ubuntu1.3 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

stab_xcoff_builtin_type in stabs.c in GNU Binutils through 2.37 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write. NOTE: this issue exists because of an incorrect fix for CVE-2018-12699.

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Use After Free

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.2-1ubuntu1.2 and dbus/libdbus-1-3@1.12.2-1ubuntu1.2
  • Fixed in: 1.12.2-1ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus@1.12.2-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus/libdbus-1-3@1.12.2-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use-after-free flaw was found in D-Bus Development branch <= 1.13.16, dbus-1.12.x stable branch <= 1.12.18, and dbus-1.10.x and older branches <= 1.10.30 when a system has multiple usernames sharing the same UID. When a set of policy rules references these usernames, D-Bus may free some memory in the heap, which is still used by data structures necessary for the other usernames sharing the UID, possibly leading to a crash or other undefined behaviors

Remediation

Upgrade Ubuntu:18.04 dbus to version 1.12.2-1ubuntu1.3 or higher.

References

low severity

CVE-2023-26604

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" command may be executed. Specifically, systemd does not set LESSSECURE to 1, and thus other programs may be launched from the less program. This presents a substantial security risk when running systemctl from Sudo, because less executes as root when the terminal size is too small to show the complete systemctl output.

Remediation

There is no fixed version for Ubuntu:18.04 systemd.

References

low severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.38

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.38 or higher.

References

low severity

Privilege Chaining

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.38

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.38 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21ubuntu1
  • Fixed in: 6.0-21ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter unzip@6.0-21ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

Remediation

Upgrade Ubuntu:18.04 unzip to version 6.0-21ubuntu1.1 or higher.

References

low severity

CVE-2018-7738

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.31.1-0.4ubuntu3.4, util-linux/fdisk@2.31.1-0.4ubuntu3.4 and others
  • Fixed in: 2.31.1-0.4ubuntu3.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/fdisk@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/libblkid1@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/libfdisk1@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/libmount1@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/libsmartcols1@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/libuuid1@2.31.1-0.4ubuntu3.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter util-linux/mount@2.31.1-0.4ubuntu3.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

Remediation

Upgrade Ubuntu:18.04 util-linux to version 2.31.1-0.4ubuntu3.7 or higher.

References

low severity

Arbitrary Command Injection

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.8 or higher.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, has a memory leak via a crafted string, leading to a denial of service (memory consumption), as demonstrated by cxxfilt, a related issue to CVE-2018-12698.

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.18

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.18 or higher.

References

low severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.10

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.10 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.2 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.8.1-2ubuntu2 and freetype/libfreetype6-dev@2.8.1-2ubuntu2
  • Fixed in: 2.8.1-2ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6@2.8.1-2ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter freetype/libfreetype6-dev@2.8.1-2ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request.

Remediation

Upgrade Ubuntu:18.04 freetype to version 2.8.1-2ubuntu2.2 or higher.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.

Remediation

There is no fixed version for Ubuntu:18.04 glibc.

References

low severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) before 2.28, parse_reg_exp in posix/regcomp.c misparses alternatives, which allows attackers to cause a denial of service (assertion failure and application exit) or trigger an incorrect result by attempting a regular-expression match.

Remediation

There is no fixed version for Ubuntu:18.04 glibc.

References

low severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid input sequences in the ISO-2022-JP-3 encoding, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: gmp/libgmp10
  • Introduced through: gmp/libgmp10@2:6.1.2+dfsg-2
  • Fixed in: 2:6.1.2+dfsg-2ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gmp/libgmp10@2:6.1.2+dfsg-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gmp package and not the gmp package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Multiple Precision Arithmetic Library (GMP) through 6.2.1 has an mpz/inp_raw.c integer overflow and resultant buffer overflow via crafted input, leading to a segmentation fault on 32-bit platforms.

Remediation

Upgrade Ubuntu:18.04 gmp to version 2:6.1.2+dfsg-2ubuntu0.1 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: gnupg2
  • Introduced through: gnupg2@2.2.4-1ubuntu1.2, gnupg2/dirmngr@2.2.4-1ubuntu1.2 and others
  • Fixed in: 2.2.4-1ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/dirmngr@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-l10n@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-utils@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-agent@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-client@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-server@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgconf@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgsm@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgv@2.2.4-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network, and GnuPG through 2.2.16, makes it risky to have a GnuPG keyserver configuration line referring to a host on the SKS keyserver network. Retrieving data from this network may cause a persistent denial of service, because of a Certificate Spamming Attack.

Remediation

Upgrade Ubuntu:18.04 gnupg2 to version 2.2.4-1ubuntu1.5 or higher.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg2
  • Introduced through: gnupg2@2.2.4-1ubuntu1.2, gnupg2/dirmngr@2.2.4-1ubuntu1.2 and others
  • Fixed in: 2.2.4-1ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/dirmngr@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-l10n@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-utils@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-agent@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-client@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-server@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgconf@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgsm@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgv@2.2.4-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 gnupg2 to version 2.2.4-1ubuntu1.3 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

Remediation

There is no fixed version for Ubuntu:18.04 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4ubuntu1.1
  • Fixed in: 1.8.1-4ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libgcrypt20@1.8.1-4ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

Remediation

Upgrade Ubuntu:18.04 libgcrypt20 to version 1.8.1-4ubuntu1.3 or higher.

References

low severity

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg-turbo8
  • Introduced through: libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4 and libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4
  • Fixed in: 1.5.2-0ubuntu5.18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8@1.5.2-0ubuntu5.18.04.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libjpeg-turbo/libjpeg-turbo8-dev@1.5.2-0ubuntu5.18.04.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjpeg-turbo package and not the libjpeg-turbo package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

Upgrade Ubuntu:18.04 libjpeg-turbo to version 1.5.2-0ubuntu5.18.04.6 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4 and openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4
  • Fixed in: 2.4.45+dfsg-1ubuntu1.11+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-2.4-2@2.4.45+dfsg-1ubuntu1.4
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openldap/libldap-common@2.4.45+dfsg-1ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

Remediation

Upgrade Ubuntu:18.04 openldap to version 2.4.45+dfsg-1ubuntu1.11+esm1 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.22

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A security vulnerability has been identified in all supported versions

of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.22 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.8

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.8 or higher.

References

low severity

Double Free

  • Vulnerable module: patch
  • Introduced through: patch@2.7.6-2ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter patch@2.7.6-2ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.

Remediation

There is no fixed version for Ubuntu:18.04 patch.

References

low severity

Out-of-bounds Read

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-9
  • Fixed in: 2:8.39-9ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pcre3/libpcre3@2:8.39-9

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.

Remediation

Upgrade Ubuntu:18.04 pcre3 to version 2:8.39-9ubuntu0.1 or higher.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-9

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pcre3/libpcre3@2:8.39-9

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

Remediation

There is no fixed version for Ubuntu:18.04 pcre3.

References

low severity

Buffer Overflow

  • Vulnerable module: perl
  • Introduced through: perl@5.26.1-6ubuntu0.3, perl/libperl5.26@5.26.1-6ubuntu0.3 and others
  • Fixed in: 5.26.1-6ubuntu0.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/libperl5.26@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-base@5.26.1-6ubuntu0.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter perl/perl-modules-5.26@5.26.1-6ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

Remediation

Upgrade Ubuntu:18.04 perl to version 5.26.1-6ubuntu0.5 or higher.

References

low severity

Incorrect Calculation

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

library/glob.html in the Python 2 and 3 documentation before 2016 has potentially misleading information about whether sorting occurs, as demonstrated by irreproducible cancer-research results. NOTE: the effects of this documentation cross application domains, and thus it is likely that security-relevant code elsewhere is affected. This issue is not a Python implementation bug, and there are no reports that NMR researchers were specifically relying on library/glob.html. In other words, because the older documentation stated "finds all the pathnames matching a specified pattern according to the rules used by the Unix shell," one might have incorrectly inferred that the sorting that occurs in a Unix shell also occurred for glob.glob. There is a workaround in newer versions of Willoughby nmr-data_compilation-p2.py and nmr-data_compilation-p3.py, which call sort() directly.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.1 or higher.

References

low severity

Resource Exhaustion

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Lib/zipfile.py in Python through 3.7.2 allows remote attackers to cause a denial of service (resource consumption) via a ZIP bomb.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.1 or higher.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: pyxdg/python3-xdg
  • Introduced through: pyxdg/python3-xdg@0.25-4ubuntu1
  • Fixed in: 0.25-4ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pyxdg/python3-xdg@0.25-4ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pyxdg package and not the pyxdg package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to trigger xdg.Menu.parse parsing within the directory containing this file. This is due to a lack of sanitization in xdg/Menu.py before an eval call.

Remediation

Upgrade Ubuntu:18.04 pyxdg to version 0.25-4ubuntu1.1 or higher.

References

low severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.3 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In SQLite through 3.22.0, databases whose schema is corrupted using a CREATE TABLE AS statement could cause a NULL pointer dereference, related to build.c and prepare.c.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.4 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.5 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1
  • Fixed in: 1.29b-2ubuntu0.2

low severity

Key Management Errors

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In the client side of Heimdal before 7.6.0, failure to verify anonymous PKINIT PA-PKINIT-KX key exchange permits a man-in-the-middle attack. This issue is in krb5_init_creds_step in lib/krb5/init_creds_pw.c.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1 or higher.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use-after-free vulnerability introduced in glibc upstream version 2.14 was found in the way the tilde expansion was carried out. Directory paths containing an initial tilde followed by a valid username were affected by this issue. A local attacker could exploit this flaw by creating a specially crafted path that, when processed by the glob function, would potentially lead to arbitrary code execution. This was fixed in version 2.32.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.28-1ubuntu1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter coreutils@8.28-1ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

There is no fixed version for Ubuntu:18.04 coreutils.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.17

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.17 or higher.

References

low severity

CVE-2023-34969

  • Vulnerable module: dbus
  • Introduced through: dbus@1.12.2-1ubuntu1.2 and dbus/libdbus-1-3@1.12.2-1ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus@1.12.2-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter dbus/libdbus-1-3@1.12.2-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream dbus package and not the dbus package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon. If a privileged user with control over the dbus-daemon is using the org.freedesktop.DBus.Monitoring interface to monitor message bus traffic, then an unprivileged user with the ability to connect to the same dbus-daemon can cause a dbus-daemon crash under some circumstances via an unreplyable message. When done on the well-known system bus, this is a denial-of-service vulnerability. The fixed versions are 1.12.28, 1.14.8, and 1.15.6.

Remediation

There is no fixed version for Ubuntu:18.04 dbus.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1ubuntu1.1
  • Fixed in: 3.5.18-1ubuntu1.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnutls28/libgnutls30@3.5.18-1ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances.

Remediation

Upgrade Ubuntu:18.04 gnutls28 to version 3.5.18-1ubuntu1.6 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-1 and others
  • Fixed in: 7.5.0+dfsg-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libasn1-8-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libgssapi3-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhcrypto4-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimbase1-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libheimntlm0-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libhx509-5-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libkrb5-26-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libroken18-heimdal@7.5.0+dfsg-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter heimdal/libwind0-heimdal@7.5.0+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ (Ticket Granting Server - Request). An authenticated user could use this flaw to crash the samba server.

Remediation

Upgrade Ubuntu:18.04 heimdal to version 7.5.0+dfsg-1ubuntu0.1 or higher.

References

low severity

CVE-2018-14048

  • Vulnerable module: libpng1.6/libpng-dev
  • Introduced through: libpng1.6/libpng-dev@1.6.34-1ubuntu0.18.04.2 and libpng1.6/libpng16-16@1.6.34-1ubuntu0.18.04.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libpng1.6/libpng-dev@1.6.34-1ubuntu0.18.04.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libpng1.6/libpng16-16@1.6.34-1ubuntu0.18.04.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue has been found in libpng 1.6.34. It is a SEGV in the function png_free_data in png.c, related to the recommended error handling for png_read_image.

Remediation

There is no fixed version for Ubuntu:18.04 libpng1.6.

References

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1+esm2 or higher.

References

low severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: python-cryptography/python3-cryptography
  • Introduced through: python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-cryptography/python3-cryptography@2.1.4-1ubuntu1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-cryptography package and not the python-cryptography package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions Cipher.update_into would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as bytes) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since update_into was originally introduced in cryptography 1.8.

Remediation

There is no fixed version for Ubuntu:18.04 python-cryptography.

References

low severity

Divide By Zero

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1
  • Fixed in: 3.22.0-1ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter sqlite3/libsqlite3-0@3.22.0-1ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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."

Remediation

Upgrade Ubuntu:18.04 sqlite3 to version 3.22.0-1ubuntu0.2 or higher.

References

low severity

Authentication Bypass

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.49

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.49 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.9+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.9+esm4 or higher.

References

low severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm1 or higher.

References

low severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

Remediation

There is no fixed version for Ubuntu:18.04 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm1 or higher.

References

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.6+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.6+esm1 or higher.

References

low severity

Resource Exhaustion

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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. This is fixed in: v3.5.10, v3.5.10rc1; v3.6.12; v3.7.9; v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1; v3.9.0, v3.9.0b4, v3.9.0b5, v3.9.0rc1, v3.9.0rc2.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.1 or higher.

References

low severity

Information Exposure

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.4-1 and nettle/libnettle6@3.4-1
  • Fixed in: 3.4.1-0ubuntu0.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libhogweed4@3.4-1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter nettle/libnettle6@3.4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nettle package and not the nettle package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A Bleichenbacher type side-channel based padding oracle attack was found in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run a process on the same physical core as the victim process, could use this flaw extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

Upgrade Ubuntu:18.04 nettle to version 3.4.1-0ubuntu0.18.04.1 or higher.

References

low severity

CVE-2021-3572

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.

Remediation

There is no fixed version for Ubuntu:18.04 python-pip.

References

low severity

Information Exposure

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There's a flaw in Python 3's pydoc. A local or adjacent attacker who discovers or is able to convince another local or adjacent user to start a pydoc server could access the server and use it to disclose sensitive information belonging to the other user that they would not normally be able to access. The highest risk of this flaw is to data confidentiality. This flaw affects Python versions before 3.8.9, Python versions before 3.9.3 and Python versions before 3.10.0a7.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.7 or higher.

References

low severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.18-1ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnutls28/libgnutls30@3.5.18-1ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Remediation

There is no fixed version for Ubuntu:18.04 gnutls28.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU binutils gold gold v1.11-v1.16 (GNU binutils v2.21-v2.31.1) is affected by: Improper Input Validation, Signed/Unsigned Comparison, Out-of-bounds Read. The impact is: Denial of service. The component is: gold/fileread.cc:497, elfcpp/elfcpp_file.h:644. The attack vector is: An ELF file with an invalid e_shoff header field must be opened.

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.

Remediation

There is no fixed version for Ubuntu:18.04 binutils.

References

low severity

Use After Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.30-21ubuntu1~18.04.3, binutils/binutils-common@2.30-21ubuntu1~18.04.3 and others
  • Fixed in: 2.30-21ubuntu1~18.04.7

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-common@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/binutils-x86-64-linux-gnu@2.30-21ubuntu1~18.04.3
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter binutils/libbinutils@2.30-21ubuntu1~18.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A use after free issue exists in the Binary File Descriptor (BFD) library (aka libbfd) in GNU Binutils 2.34 in bfd_hash_lookup, as demonstrated in nm-new, that can cause a denial of service via a crafted file.

Remediation

Upgrade Ubuntu:18.04 binutils to version 2.30-21ubuntu1~18.04.7 or higher.

References

low severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24 or higher.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid multi-byte input sequences in IBM1364, IBM1371, IBM1388, IBM1390, and IBM1399 encodings, fails to advance the input state, which could lead to an infinite loop in applications, resulting in a denial of service, a different vulnerability from CVE-2016-10228.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long double function contains a non-canonical bit pattern, a seen when passing a 0x5d414141414141410000 value to sinl on x86 targets. This is related to sysdeps/ieee754/ldbl-96/e_rem_pio2l.c.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libpng1.6/libpng-dev
  • Introduced through: libpng1.6/libpng-dev@1.6.34-1ubuntu0.18.04.2 and libpng1.6/libpng16-16@1.6.34-1ubuntu0.18.04.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libpng1.6/libpng-dev@1.6.34-1ubuntu0.18.04.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libpng1.6/libpng16-16@1.6.34-1ubuntu0.18.04.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Rejected reason: Maintainer contacted. This is a false-positive. The flaw does not actually exist and was erroneously tested.

Remediation

There is no fixed version for Ubuntu:18.04 libpng1.6.

References

low severity

CVE-2024-0727

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.23+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.23+esm4 or higher.

References

low severity

Release of Invalid Pointer or Reference

  • Vulnerable module: patch
  • Introduced through: patch@2.7.6-2ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter patch@2.7.6-2ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.

Remediation

There is no fixed version for Ubuntu:18.04 patch.

References

low severity

Improper Authentication

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1ubuntu2 and shadow/passwd@1:4.5-1ubuntu2
  • Fixed in: 1:4.5-1ubuntu2.5+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/login@1:4.5-1ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/passwd@1:4.5-1ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.

Remediation

Upgrade Ubuntu:18.04 shadow to version 1:4.5-1ubuntu2.5+esm1 or higher.

References

low severity

CVE-2022-0530

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21ubuntu1
  • Fixed in: 6.0-21ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter unzip@6.0-21ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Ubuntu:18.04 unzip to version 6.0-21ubuntu1.2 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@6.1-1ubuntu1.18.04, ncurses/libncursesw5@6.1-1ubuntu1.18.04 and others
  • Fixed in: 6.1-1ubuntu1.18.04.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncurses5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libncursesw5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/libtinfo5@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-base@6.1-1ubuntu1.18.04
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter ncurses/ncurses-bin@6.1-1ubuntu1.18.04

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Ubuntu:18.04 ncurses to version 6.1-1ubuntu1.18.04.1 or higher.

References

low severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.23+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.23+esm3 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.22

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.

As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.

Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.

Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.22 or higher.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.22

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.

Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.22 or higher.

References

low severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.23+esm4

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.23+esm4 or higher.

References

low severity

Inefficient Regular Expression Complexity

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.23+esm3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.23+esm3 or higher.

References

low severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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 Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.6 or higher.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.6 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-9
  • Fixed in: 2:8.39-9ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter pcre3/libpcre3@2:8.39-9

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.

Remediation

Upgrade Ubuntu:18.04 pcre3 to version 2:8.39-9ubuntu0.1 or higher.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1ubuntu2 and shadow/passwd@1:4.5-1ubuntu2
  • Fixed in: 1:4.5-1ubuntu2.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/login@1:4.5-1ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/passwd@1:4.5-1ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in shadow 4.5. newgidmap (in shadow-utils) is setuid and allows an unprivileged user to be placed in a user namespace where setgroups(2) is permitted. This allows an attacker to remove themselves from a supplementary group, which may allow access to certain filesystem paths if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. This flaw effectively reverts a security feature in the kernel (in particular, the /proc/self/setgroups knob) to prevent this sort of privilege escalation.

Remediation

Upgrade Ubuntu:18.04 shadow to version 1:4.5-1ubuntu2.2 or higher.

References

low severity

Reachable Assertion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The iconv function in the GNU C Library (aka glibc or libc6) 2.30 to 2.32, when converting UCS4 text containing an irreversible character, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.5 or higher.

References

low severity

CVE-2019-1547

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.6 or higher.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1ubuntu2 and shadow/passwd@1:4.5-1ubuntu2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/login@1:4.5-1ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/passwd@1:4.5-1ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

Remediation

There is no fixed version for Ubuntu:18.04 shadow.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1
  • Fixed in: 1.29b-2ubuntu0.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter tar@1.29b-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root).

Remediation

Upgrade Ubuntu:18.04 tar to version 1.29b-2ubuntu0.2 or higher.

References

low severity

CVE-2020-8284

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.12

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.12 or higher.

References

low severity

CVE-2022-35252

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.20

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.20 or higher.

References

low severity

CVE-2023-28322

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm1 or higher.

References

low severity

CVE-2023-38546

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.24+esm2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.24+esm2 or higher.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1-1ubuntu2.1~18.04.5 and openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5
  • Fixed in: 1.1.1-1ubuntu2.1~18.04.6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl@1.1.1-1ubuntu2.1~18.04.5
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter openssl/libssl1.1@1.1.1-1ubuntu2.1~18.04.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

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).

Remediation

Upgrade Ubuntu:18.04 openssl to version 1.1.1-1ubuntu2.1~18.04.6 or higher.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.27-3ubuntu1, glibc/libc-dev-bin@2.27-3ubuntu1 and others
  • Fixed in: 2.27-3ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc-dev-bin@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/libc6-dev@2.27-3ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter glibc/multiarch-support@2.27-3ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.

Remediation

Upgrade Ubuntu:18.04 glibc to version 2.27-3ubuntu1.2 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2
  • Introduced through: gnupg2@2.2.4-1ubuntu1.2, gnupg2/dirmngr@2.2.4-1ubuntu1.2 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/dirmngr@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-l10n@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gnupg-utils@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-agent@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-client@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpg-wks-server@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgconf@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgsm@2.2.4-1ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter gnupg2/gpgv@2.2.4-1ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Ubuntu:18.04 gnupg2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 2.7-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a heap-based buffer over-read in ebitmap_match_any (called indirectly from cil_check_neverallow). This occurs because there is sometimes a lack of checks for invalid statements in an optional block.

Remediation

Upgrade Ubuntu:18.04 libsepol to version 2.7-1ubuntu0.1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 2.7-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and cil_reset_classperms_list).

Remediation

Upgrade Ubuntu:18.04 libsepol to version 2.7-1ubuntu0.1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 2.7-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __cil_verify_classpermission and __cil_pre_verify_helper).

Remediation

Upgrade Ubuntu:18.04 libsepol to version 2.7-1ubuntu0.1 or higher.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.7-1
  • Fixed in: 2.7-1ubuntu0.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libsepol/libsepol1@2.7-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __verify_map_perm_classperms and hashtab_map).

Remediation

Upgrade Ubuntu:18.04 libsepol to version 2.7-1ubuntu0.1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: procps
  • Introduced through: procps@2:3.3.12-3ubuntu1.2 and procps/libprocps6@2:3.3.12-3ubuntu1.2
  • Fixed in: 2:3.3.12-3ubuntu1.2+esm1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter procps@2:3.3.12-3ubuntu1.2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter procps/libprocps6@2:3.3.12-3ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.

Remediation

Upgrade Ubuntu:18.04 procps to version 2:3.3.12-3ubuntu1.2+esm1 or higher.

References

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1ubuntu2 and shadow/passwd@1:4.5-1ubuntu2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/login@1:4.5-1ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/passwd@1:4.5-1ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

Remediation

There is no fixed version for Ubuntu:18.04 shadow.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-2ubuntu0.1
  • Fixed in: 1.29b-2ubuntu0.3

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter tar@1.29b-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Ubuntu:18.04 tar to version 1.29b-2ubuntu0.3 or higher.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21ubuntu1
  • Fixed in: 6.0-21ubuntu1.2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter unzip@6.0-21ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A flaw was found in unzip. The vulnerability occurs due to improper handling of Unicode strings, which can lead to a null pointer dereference. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Remediation

Upgrade Ubuntu:18.04 unzip to version 6.0-21ubuntu1.2 or higher.

References

low severity

Resource Exhaustion

  • Vulnerable module: unzip
  • Introduced through: unzip@6.0-21ubuntu1
  • Fixed in: 6.0-21ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter unzip@6.0-21ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream unzip package and not the unzip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

Remediation

Upgrade Ubuntu:18.04 unzip to version 6.0-21ubuntu1.1 or higher.

References

low severity

Missing Initialization of Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.58.0-2ubuntu3.9, curl/libcurl3-gnutls@7.58.0-2ubuntu3.9 and others
  • Fixed in: 7.58.0-2ubuntu3.14

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl3-gnutls@7.58.0-2ubuntu3.9
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter curl/libcurl4@7.58.0-2ubuntu3.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

curl 7.7 through 7.76.1 suffers from an information disclosure when the -t command line option, known as CURLOPT_TELNETOPTIONS in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.

Remediation

Upgrade Ubuntu:18.04 curl to version 7.58.0-2ubuntu3.14 or higher.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@237-3ubuntu10.31 and systemd/libudev1@237-3ubuntu10.31
  • Fixed in: 237-3ubuntu10.38

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libsystemd0@237-3ubuntu10.31
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter systemd/libudev1@237-3ubuntu10.31

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.

Remediation

Upgrade Ubuntu:18.04 systemd to version 237-3ubuntu10.38 or higher.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Remediation

There is no fixed version for Ubuntu:18.04 krb5.

References

low severity

Memory Leak

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.16-2ubuntu0.1, krb5/libk5crypto3@1.16-2ubuntu0.1 and others

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libgssapi-krb5-2@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libk5crypto3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5-3@1.16-2ubuntu0.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter krb5/libkrb5support0@1.16-2ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

Remediation

There is no fixed version for Ubuntu:18.04 krb5.

References

low severity

Information Exposure

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.1-4ubuntu1.1

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter libgcrypt20@1.8.1-4ubuntu1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Ubuntu:18.04 libgcrypt20.

References

low severity

CVE-2024-37891

  • Vulnerable module: python-pip/python-pip-whl
  • Introduced through: python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1 and python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1
  • Fixed in: 9.0.1-2.3~ubuntu1.18.04.8+esm6

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python-pip-whl@9.0.1-2.3~ubuntu1.18.04.1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python-pip/python3-pip@9.0.1-2.3~ubuntu1.18.04.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected. However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the Proxy-Authorization HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the Proxy-Authorization header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the Proxy-Authorization header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach. We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: 1. Setting the Proxy-Authorization header without using urllib3's built-in proxy support. 2. Not disabling HTTP redirects. 3. Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2. Users unable to upgrade may use the Proxy-Authorization header with urllib3's ProxyManager, disable HTTP redirects using redirects=False when sending requests, or not user the Proxy-Authorization header as mitigations.

Remediation

Upgrade Ubuntu:18.04 python-pip to version 9.0.1-2.3~ubuntu1.18.04.8+esm6 or higher.

References

low severity

CVE-2025-1795

  • Vulnerable module: python3.6
  • Introduced through: python3.6@3.6.9-1~18.04ubuntu1, python3.6/libpython3.6@3.6.9-1~18.04ubuntu1 and others
  • Fixed in: 3.6.9-1~18.04ubuntu1.13+esm5

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-minimal@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/libpython3.6-stdlib@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-dev@3.6.9-1~18.04ubuntu1
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter python3.6/python3.6-minimal@3.6.9-1~18.04ubuntu1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3.6 package and not the python3.6 package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.

Remediation

Upgrade Ubuntu:18.04 python3.6 to version 3.6.9-1~18.04ubuntu1.13+esm5 or higher.

References

low severity

CVE-2024-56433

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1ubuntu2 and shadow/passwd@1:4.5-1ubuntu2

Detailed paths

  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/login@1:4.5-1ubuntu2
  • Introduced through: tensorflow/tensorflow@2.3.0rc0-gpu-jupyter shadow/passwd@1:4.5-1ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:18.04 relevant fixed versions and status.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Ubuntu:18.04 shadow.

References