Skip to content

1.117.0

Compare
Choose a tag to compare
@cf-buildpacks-eng cf-buildpacks-eng released this 22 Aug 15:20
· 95 commits to main since this release

Notably, this release addresses:

USN-6964-1 ORC vulnerability:

  • CVE-2024-40897:
    Stack-based buffer overflow vulnerability exists in orcparse.c of ORC
    versions prior to 0.4.39. If a developer is tricked to process a specially
    crafted file with the affected ORC compiler, an arbitrary code may be
    executed on the developer's build environment. This may lead to compromise
    of developer machines or CI build environments.

USN-6947-1 Kerberos vulnerabilities:

  • CVE-2024-37371:
    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.
  • CVE-2024-37370:
    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.

USN-6944-1 curl vulnerability:

  • CVE-2024-7264:
    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.

USN-6937-1 OpenSSL vulnerabilities:

  • CVE-2024-4741:
    Use After Free with SSL_free_buffers
  • CVE-2024-2511:
    Issue summary: Some non-default TLS server configurations can cause
    unbounded memory growth when processing TLSv1.3 sessions Impact summary: An
    attacker may exploit certain server configurations to trigger unbounded
    memory growth that would lead to a Denial of Service This problem can occur
    in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but
    not if early_data support is also configured and the default anti-replay
    protection is in use). In this case, under certain conditions, the session
    cache can get into an incorrect state and it will fail to flush properly as
    it fills. The session cache will continue to grow in an unbounded manner. A
    malicious client could deliberately create the scenario for this failure to
    force a Denial of Service. It may also happen by accident in normal
    operation. This issue only affects TLS servers supporting TLSv1.3. It does
    not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not
    affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
  • CVE-2024-5535:
    Issue summary: Calling the OpenSSL API function SSL_select_next_proto with
    an
    empty supported client protocols buffer may cause a crash or memory
    contents to
    be sent to the peer.
    Impact summary: A buffer overread can have a range of potential
    consequences
    such as unexpected application beahviour or a crash. In particular this
    issue
    could result in up to 255 bytes of arbitrary private data from memory being
    sent
    to the peer leading to a loss of confidentiality. However, only
    applications
    that directly call the SSL_select_next_proto function with a 0 length list
    of
    supported client protocols are affected by this issue. This would normally
    never
    be a valid scenario and is typically not under attacker control but may
    occur by
    accident in the case of a configuration or programming error in the calling
    application.
    The OpenSSL API function SSL_select_next_proto is typically used by TLS
    applications that support ALPN (Application Layer Protocol Negotiation) or
    NPN
    (Next Protocol Negotiation). NPN is older, was never standardised and
    is deprecated in favour of ALPN. We believe that ALPN is significantly more
    widely deployed than NPN. The SSL_select_next_proto function accepts a list
    of
    protocols from the server and a list of protocols from the client and
    returns
    the first protocol that appears in the server list that also appears in the
    client list. In the case of no overlap between the two lists it returns the
    first item in the client list. In either case it will signal whether an
    overlap
    between the two lists was found. In the case where SSL_select_next_proto is
    called with a zero length client list it fails to notice this condition and
    returns the memory immediately following the client list pointer (and
    reports
    that there was no overlap in the lists).
    This function is typically called from a server side application callback
    for
    ALPN or a client side application callback for NPN. In the case of ALPN the
    list
    of protocols supplied by the client is guaranteed by libssl to never be
    zero in
    length. The list of server protocols comes from the application and should
    never
    normally be expected to be of zero length. In this case if the
    SSL_select_next_proto function has been called as expected (with the list
    supplied by the client passed in the client/client_len parameters), then
    the
    application will not be vulnerable to this issue. If the application has
    accidentally been configured with a zero length server list, and has
    accidentally passed that zero length server list in the client/client_len
    parameters, and has additionally failed to correctly handle a "no overlap"
    response (which would normally result in a handshake failure in ALPN) then
    it
    will be vulnerable to this problem.
    In the case of NPN, the protocol permits the client to opportunistically
    select
    a protocol when there is no overlap. OpenSSL returns the first client
    protocol
    in the no overlap case in support of this. The list of client protocols
    comes
    from the application and should never normally be expected to be of zero
    length.
    However if the SSL_select_next_proto function is accidentally called with a
    client_len of 0 then an invalid memory pointer will be returned instead. If
    the
    application uses this output as the opportunistic protocol then the loss of
    confidentiality will occur.
    This issue has been assessed as Low severity because applications are most
    likely to be vulnerable if they are using NPN instead of ALPN - but NPN is
    not
    widely used. It also requires an application configuration or programming
    error.
    Finally, this issue would not typically be under attacker control making
    active
    exploitation unlikely.
    The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
    Due to the low severity of this issue we are not issuing new releases of
    OpenSSL at this time. The fix will be included in the next releases when
    they
    become available.
  • CVE-2024-4603:
    Issue summary: Checking excessively long DSA keys or parameters may be very
    slow. Impact summary: Applications that use the functions
    EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key
    or DSA 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 functions EVP_PKEY_param_check() or
    EVP_PKEY_public_check() perform various checks on DSA parameters. Some of
    those computations take a long time if the modulus (p parameter) is too
    large. Trying to use a very large modulus is slow and OpenSSL will not
    allow using public keys with a modulus which is over 10,000 bits in length
    for signature verification. However the key and parameter check functions
    do not limit the modulus size when performing the checks. An application
    that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a
    key or parameters obtained from an untrusted source could be vulnerable to
    a Denial of Service attack. These functions are not called by OpenSSL
    itself on untrusted DSA keys so only applications that directly call these
    functions may be vulnerable. Also vulnerable are the OpenSSL pkey 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 affected by this issue.
-ii  curl                        7.81.0-1ubuntu1.16     amd64 command line tool for transferring data with URL syntax
+ii  curl                        7.81.0-1ubuntu1.17     amd64 command line tool for transferring data with URL syntax
-ii  krb5-multidev:amd64         1.19.2-2ubuntu0.3      amd64 development files for MIT Kerberos without Heimdal conflict
-ii  krb5-user                   1.19.2-2ubuntu0.3      amd64 basic programs to authenticate using MIT Kerberos
+ii  krb5-multidev:amd64         1.19.2-2ubuntu0.4      amd64 development files for MIT Kerberos without Heimdal conflict
+ii  krb5-user                   1.19.2-2ubuntu0.4      amd64 basic programs to authenticate using MIT Kerberos
-ii  libcurl3-gnutls:amd64       7.81.0-1ubuntu1.16     amd64 easy-to-use client-side URL transfer library (GnuTLS flavour)
-ii  libcurl4:amd64              7.81.0-1ubuntu1.16     amd64 easy-to-use client-side URL transfer library (OpenSSL flavour)
-ii  libcurl4-openssl-dev:amd64  7.81.0-1ubuntu1.16     amd64 development files and documentation for libcurl (OpenSSL flavour)
+ii  libcurl3-gnutls:amd64       7.81.0-1ubuntu1.17     amd64 easy-to-use client-side URL transfer library (GnuTLS flavour)
+ii  libcurl4:amd64              7.81.0-1ubuntu1.17     amd64 easy-to-use client-side URL transfer library (OpenSSL flavour)
+ii  libcurl4-openssl-dev:amd64  7.81.0-1ubuntu1.17     amd64 development files and documentation for libcurl (OpenSSL flavour)
-ii  libgssapi-krb5-2:amd64      1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - krb5 GSS-API Mechanism
+ii  libgssapi-krb5-2:amd64      1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - krb5 GSS-API Mechanism
-ii  libgssrpc4:amd64            1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - GSS enabled ONCRPC
+ii  libgssrpc4:amd64            1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - GSS enabled ONCRPC
-ii  libk5crypto3:amd64          1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - Crypto Library
-ii  libkadm5clnt-mit12:amd64    1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - Administration Clients
-ii  libkadm5srv-mit12:amd64     1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - KDC and Admin Server
-ii  libkdb5-10:amd64            1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - Kerberos database
+ii  libk5crypto3:amd64          1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - Crypto Library
+ii  libkadm5clnt-mit12:amd64    1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - Administration Clients
+ii  libkadm5srv-mit12:amd64     1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - KDC and Admin Server
+ii  libkdb5-10:amd64            1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - Kerberos database
-ii  libkrb5-3:amd64             1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries
-ii  libkrb5-dev:amd64           1.19.2-2ubuntu0.3      amd64 headers and development libraries for MIT Kerberos
-ii  libkrb5support0:amd64       1.19.2-2ubuntu0.3      amd64 MIT Kerberos runtime libraries - Support library
+ii  libkrb5-3:amd64             1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries
+ii  libkrb5-dev:amd64           1.19.2-2ubuntu0.4      amd64 headers and development libraries for MIT Kerberos
+ii  libkrb5support0:amd64       1.19.2-2ubuntu0.4      amd64 MIT Kerberos runtime libraries - Support library
-ii  liborc-0.4-0:amd64          1:0.4.32-2             amd64 Library of Optimized Inner Loops Runtime Compiler
+ii  liborc-0.4-0:amd64          1:0.4.32-2ubuntu0.1    amd64 Library of Optimized Inner Loops Runtime Compiler
-ii  libpq-dev                   14.12-0ubuntu0.22.04.1 amd64 header files for libpq5 (PostgreSQL library)
-ii  libpq5:amd64                14.12-0ubuntu0.22.04.1 amd64 PostgreSQL C client library
+ii  libpq-dev                   14.13-0ubuntu0.22.04.1 amd64 header files for libpq5 (PostgreSQL library)
+ii  libpq5:amd64                14.13-0ubuntu0.22.04.1 amd64 PostgreSQL C client library
-ii  libpython3.10:amd64         3.10.12-1~22.04.4      amd64 Shared Python runtime library (version 3.10)
-ii  libpython3.10-minimal:amd64 3.10.12-1~22.04.4      amd64 Minimal subset of the Python language (version 3.10)
-ii  libpython3.10-stdlib:amd64  3.10.12-1~22.04.4      amd64 Interactive high-level object-oriented language (standard library, version 3.10)
+ii  libpython3.10:amd64         3.10.12-1~22.04.5      amd64 Shared Python runtime library (version 3.10)
+ii  libpython3.10-minimal:amd64 3.10.12-1~22.04.5      amd64 Minimal subset of the Python language (version 3.10)
+ii  libpython3.10-stdlib:amd64  3.10.12-1~22.04.5      amd64 Interactive high-level object-oriented language (standard library, version 3.10)
-ii  libssl-dev:amd64            3.0.2-0ubuntu1.16      amd64 Secure Sockets Layer toolkit - development files
-ii  libssl3:amd64               3.0.2-0ubuntu1.16      amd64 Secure Sockets Layer toolkit - shared libraries
+ii  libssl-dev:amd64            3.0.2-0ubuntu1.17      amd64 Secure Sockets Layer toolkit - development files
+ii  libssl3:amd64               3.0.2-0ubuntu1.17      amd64 Secure Sockets Layer toolkit - shared libraries
-ii  linux-libc-dev:amd64        5.15.0-117.127         amd64 Linux Kernel Headers for development
+ii  linux-libc-dev:amd64        5.15.0-119.129         amd64 Linux Kernel Headers for development
-ii  openssl                     3.0.2-0ubuntu1.16      amd64 Secure Sockets Layer toolkit - cryptographic utility
+ii  openssl                     3.0.2-0ubuntu1.17      amd64 Secure Sockets Layer toolkit - cryptographic utility```