{ "summary": { "snap": { "added": [], "removed": [], "diff": [] }, "deb": { "added": [], "removed": [], "diff": [ "curl", "dracut-install", "libcurl3t64-gnutls", "libcurl4t64", "libopeniscsiusr", "libpython3.12-minimal", "libpython3.12-stdlib", "libpython3.12t64", "libssl3t64", "needrestart", "open-iscsi", "openssl", "python3.12", "python3.12-minimal", "snapd", "thin-provisioning-tools" ] } }, "diff": { "deb": [ { "name": "curl", "from_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.1", "version": "8.5.0-2ubuntu10.1" }, "to_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.2", "version": "8.5.0-2ubuntu10.2" }, "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "log": [ "", " * SECURITY UPDATE: ASN.1 date parser overread", " - debian/patches/CVE-2024-7264-pre1.patch: clean up GTime2str in", " lib/vtls/x509asn1.c.", " - debian/patches/CVE-2024-7264.patch: unittests and fixes for gtime2str", " in lib/vtls/x509asn1.c, lib/vtls/x509asn1.h, tests/data/Makefile.inc,", " tests/data/test1656, tests/unit/Makefile.inc, tests/unit/unit1656.c.", " - CVE-2024-7264", "" ], "package": "curl", "version": "8.5.0-2ubuntu10.2", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Thu, 01 Aug 2024 09:43:08 -0400" } ], "notes": null }, { "name": "dracut-install", "from_version": { "source_package_name": "dracut", "source_package_version": "060+5-1ubuntu3.1", "version": "060+5-1ubuntu3.1" }, "to_version": { "source_package_name": "dracut", "source_package_version": "060+5-1ubuntu3.2", "version": "060+5-1ubuntu3.2" }, "cves": [], "launchpad_bugs_fixed": [ 2065180 ], "changes": [ { "cves": [], "log": [ "", " * Cherry-pick upstream performance fixes (LP: #2065180):", " - perf(dracut-install): memoize find_kmod_module_from_sysfs_node", " - perf(dracut-install): use driver/module sysfs dirs for module name", " * Depend on isc-dhcp-client for upstream-dracut-network autopkgtest", "" ], "package": "dracut", "version": "060+5-1ubuntu3.2", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2065180 ], "author": "Benjamin Drung ", "date": "Mon, 08 Jul 2024 22:47:24 +0200" } ], "notes": null }, { "name": "libcurl3t64-gnutls", "from_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.1", "version": "8.5.0-2ubuntu10.1" }, "to_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.2", "version": "8.5.0-2ubuntu10.2" }, "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "log": [ "", " * SECURITY UPDATE: ASN.1 date parser overread", " - debian/patches/CVE-2024-7264-pre1.patch: clean up GTime2str in", " lib/vtls/x509asn1.c.", " - debian/patches/CVE-2024-7264.patch: unittests and fixes for gtime2str", " in lib/vtls/x509asn1.c, lib/vtls/x509asn1.h, tests/data/Makefile.inc,", " tests/data/test1656, tests/unit/Makefile.inc, tests/unit/unit1656.c.", " - CVE-2024-7264", "" ], "package": "curl", "version": "8.5.0-2ubuntu10.2", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Thu, 01 Aug 2024 09:43:08 -0400" } ], "notes": null }, { "name": "libcurl4t64", "from_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.1", "version": "8.5.0-2ubuntu10.1" }, "to_version": { "source_package_name": "curl", "source_package_version": "8.5.0-2ubuntu10.2", "version": "8.5.0-2ubuntu10.2" }, "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-7264", "url": "https://ubuntu.com/security/CVE-2024-7264", "cve_description": "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.", "cve_priority": "medium", "cve_public_date": "2024-07-31" } ], "log": [ "", " * SECURITY UPDATE: ASN.1 date parser overread", " - debian/patches/CVE-2024-7264-pre1.patch: clean up GTime2str in", " lib/vtls/x509asn1.c.", " - debian/patches/CVE-2024-7264.patch: unittests and fixes for gtime2str", " in lib/vtls/x509asn1.c, lib/vtls/x509asn1.h, tests/data/Makefile.inc,", " tests/data/test1656, tests/unit/Makefile.inc, tests/unit/unit1656.c.", " - CVE-2024-7264", "" ], "package": "curl", "version": "8.5.0-2ubuntu10.2", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Thu, 01 Aug 2024 09:43:08 -0400" } ], "notes": null }, { "name": "libopeniscsiusr", "from_version": { "source_package_name": "open-iscsi", "source_package_version": "2.1.9-3ubuntu4", "version": "2.1.9-3ubuntu4" }, "to_version": { "source_package_name": "open-iscsi", "source_package_version": "2.1.9-3ubuntu5.1", "version": "2.1.9-3ubuntu5.1" }, "cves": [], "launchpad_bugs_fixed": [ 2065180 ], "changes": [ { "cves": [], "log": [ "", " * initramfs-hook: Combine calls to manual_add_modules (LP: #2065180)", "" ], "package": "open-iscsi", "version": "2.1.9-3ubuntu5.1", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2065180 ], "author": "Benjamin Drung ", "date": "Mon, 01 Jul 2024 21:01:25 +0200" }, { "cves": [], "log": [ "", " * No-change rebuild against libmount1t64.", "" ], "package": "open-iscsi", "version": "2.1.9-3ubuntu5", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 19 Apr 2024 18:45:14 +0200" } ], "notes": null }, { "name": "libpython3.12-minimal", "from_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1", "version": "3.12.3-1" }, "to_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1ubuntu0.1", "version": "3.12.3-1ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: is_private and is_global mismatch", " - debian/patches/CVE-2024-4032.patch: fix \"private\" (non-global) IP", " address ranges in Doc/library/ipaddress.rst, Lib/ipaddress.py,", " Lib/test/test_ipaddress.py.", " - CVE-2024-4032", "" ], "package": "python3.12", "version": "3.12.3-1ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 31 Jul 2024 13:43:48 -0400" } ], "notes": null }, { "name": "libpython3.12-stdlib", "from_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1", "version": "3.12.3-1" }, "to_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1ubuntu0.1", "version": "3.12.3-1ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: is_private and is_global mismatch", " - debian/patches/CVE-2024-4032.patch: fix \"private\" (non-global) IP", " address ranges in Doc/library/ipaddress.rst, Lib/ipaddress.py,", " Lib/test/test_ipaddress.py.", " - CVE-2024-4032", "" ], "package": "python3.12", "version": "3.12.3-1ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 31 Jul 2024 13:43:48 -0400" } ], "notes": null }, { "name": "libpython3.12t64", "from_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1", "version": "3.12.3-1" }, "to_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1ubuntu0.1", "version": "3.12.3-1ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: is_private and is_global mismatch", " - debian/patches/CVE-2024-4032.patch: fix \"private\" (non-global) IP", " address ranges in Doc/library/ipaddress.rst, Lib/ipaddress.py,", " Lib/test/test_ipaddress.py.", " - CVE-2024-4032", "" ], "package": "python3.12", "version": "3.12.3-1ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 31 Jul 2024 13:43:48 -0400" } ], "notes": null }, { "name": "libssl3t64", "from_version": { "source_package_name": "openssl", "source_package_version": "3.0.13-0ubuntu3.1", "version": "3.0.13-0ubuntu3.1" }, "to_version": { "source_package_name": "openssl", "source_package_version": "3.0.13-0ubuntu3.2", "version": "3.0.13-0ubuntu3.2" }, "cves": [ { "cve": "CVE-2024-2511", "url": "https://ubuntu.com/security/CVE-2024-2511", "cve_description": "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_priority": "low", "cve_public_date": "2024-04-08 14:15:00 UTC" }, { "cve": "CVE-2024-4603", "url": "https://ubuntu.com/security/CVE-2024-4603", "cve_description": "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.", "cve_priority": "low", "cve_public_date": "2024-05-16 16:15:00 UTC" }, { "cve": "CVE-2024-4741", "url": "https://ubuntu.com/security/CVE-2024-4741", "cve_description": "Use After Free with SSL_free_buffers", "cve_priority": "low", "cve_public_date": "2024-05-28" }, { "cve": "CVE-2024-5535", "url": "https://ubuntu.com/security/CVE-2024-5535", "cve_description": "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_priority": "low", "cve_public_date": "2024-06-27 11:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-2511", "url": "https://ubuntu.com/security/CVE-2024-2511", "cve_description": "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_priority": "low", "cve_public_date": "2024-04-08 14:15:00 UTC" }, { "cve": "CVE-2024-4603", "url": "https://ubuntu.com/security/CVE-2024-4603", "cve_description": "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.", "cve_priority": "low", "cve_public_date": "2024-05-16 16:15:00 UTC" }, { "cve": "CVE-2024-4741", "url": "https://ubuntu.com/security/CVE-2024-4741", "cve_description": "Use After Free with SSL_free_buffers", "cve_priority": "low", "cve_public_date": "2024-05-28" }, { "cve": "CVE-2024-5535", "url": "https://ubuntu.com/security/CVE-2024-5535", "cve_description": "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_priority": "low", "cve_public_date": "2024-06-27 11:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: unbounded mem growth when processing TLSv1.3 sessions", " - debian/patches/CVE-2024-2511.patch: fix unconstrained session cache", " growth in TLSv1.3 in ssl/ssl_lib.c, ssl/ssl_sess.c,", " ssl/statem/statem_srvr.c.", " - CVE-2024-2511", " * SECURITY UPDATE: checking excessively long DSA keys or params very slow", " - debian/patches/CVE-2024-4603.patch: check DSA parameters for", " excessive sizes before validating in crypto/dsa/dsa_check.c,", " test/recipes/15-test_dsaparam_data/invalid/p10240_q256_too_big.pem.", " - CVE-2024-4603", " * SECURITY UPDATE: use after free with SSL_free_buffers", " - debian/patches/CVE-2024-4741.patch: only free the read buffers if", " we're not using them in ssl/record/rec_layer_s3.c,", " ssl/record/record.h, ssl/ssl_lib.c.", " - CVE-2024-4741", " * SECURITY UPDATE: crash or memory disclosure via SSL_select_next_proto", " - debian/patches/CVE-2024-5535.patch: validate provided client list in", " ssl/ssl_lib.c.", " - CVE-2024-5535", "" ], "package": "openssl", "version": "3.0.13-0ubuntu3.2", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 30 Jul 2024 11:03:13 -0400" } ], "notes": null }, { "name": "needrestart", "from_version": { "source_package_name": "needrestart", "source_package_version": "3.6-7ubuntu4", "version": "3.6-7ubuntu4" }, "to_version": { "source_package_name": "needrestart", "source_package_version": "3.6-7ubuntu4.1", "version": "3.6-7ubuntu4.1" }, "cves": [], "launchpad_bugs_fixed": [ 2067482, 2065863, 2068543, 2068573, 2063442 ], "changes": [ { "cves": [], "log": [ "", " * Prevent needrestart restarting itself (LP: #2067482)", " * d/p/ubuntu-mode.patch: Don't touch /run/reboot-required on kernel updates", " (LP: #2065863)", " * Ubuntu mode: disable it if restart mode has been explicitly set", " (LP: #2068543)", " * Add some inline documentation for the Ubuntu mode (LP: #2068573)", " * Don't restart the google-guest-agent service (LP: #2063442)", "" ], "package": "needrestart", "version": "3.6-7ubuntu4.1", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2067482, 2065863, 2068543, 2068573, 2063442 ], "author": "Simon Chopin ", "date": "Fri, 14 Jun 2024 15:37:30 +0200" } ], "notes": null }, { "name": "open-iscsi", "from_version": { "source_package_name": "open-iscsi", "source_package_version": "2.1.9-3ubuntu4", "version": "2.1.9-3ubuntu4" }, "to_version": { "source_package_name": "open-iscsi", "source_package_version": "2.1.9-3ubuntu5.1", "version": "2.1.9-3ubuntu5.1" }, "cves": [], "launchpad_bugs_fixed": [ 2065180 ], "changes": [ { "cves": [], "log": [ "", " * initramfs-hook: Combine calls to manual_add_modules (LP: #2065180)", "" ], "package": "open-iscsi", "version": "2.1.9-3ubuntu5.1", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2065180 ], "author": "Benjamin Drung ", "date": "Mon, 01 Jul 2024 21:01:25 +0200" }, { "cves": [], "log": [ "", " * No-change rebuild against libmount1t64.", "" ], "package": "open-iscsi", "version": "2.1.9-3ubuntu5", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 19 Apr 2024 18:45:14 +0200" } ], "notes": null }, { "name": "openssl", "from_version": { "source_package_name": "openssl", "source_package_version": "3.0.13-0ubuntu3.1", "version": "3.0.13-0ubuntu3.1" }, "to_version": { "source_package_name": "openssl", "source_package_version": "3.0.13-0ubuntu3.2", "version": "3.0.13-0ubuntu3.2" }, "cves": [ { "cve": "CVE-2024-2511", "url": "https://ubuntu.com/security/CVE-2024-2511", "cve_description": "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_priority": "low", "cve_public_date": "2024-04-08 14:15:00 UTC" }, { "cve": "CVE-2024-4603", "url": "https://ubuntu.com/security/CVE-2024-4603", "cve_description": "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.", "cve_priority": "low", "cve_public_date": "2024-05-16 16:15:00 UTC" }, { "cve": "CVE-2024-4741", "url": "https://ubuntu.com/security/CVE-2024-4741", "cve_description": "Use After Free with SSL_free_buffers", "cve_priority": "low", "cve_public_date": "2024-05-28" }, { "cve": "CVE-2024-5535", "url": "https://ubuntu.com/security/CVE-2024-5535", "cve_description": "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_priority": "low", "cve_public_date": "2024-06-27 11:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-2511", "url": "https://ubuntu.com/security/CVE-2024-2511", "cve_description": "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_priority": "low", "cve_public_date": "2024-04-08 14:15:00 UTC" }, { "cve": "CVE-2024-4603", "url": "https://ubuntu.com/security/CVE-2024-4603", "cve_description": "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.", "cve_priority": "low", "cve_public_date": "2024-05-16 16:15:00 UTC" }, { "cve": "CVE-2024-4741", "url": "https://ubuntu.com/security/CVE-2024-4741", "cve_description": "Use After Free with SSL_free_buffers", "cve_priority": "low", "cve_public_date": "2024-05-28" }, { "cve": "CVE-2024-5535", "url": "https://ubuntu.com/security/CVE-2024-5535", "cve_description": "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_priority": "low", "cve_public_date": "2024-06-27 11:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: unbounded mem growth when processing TLSv1.3 sessions", " - debian/patches/CVE-2024-2511.patch: fix unconstrained session cache", " growth in TLSv1.3 in ssl/ssl_lib.c, ssl/ssl_sess.c,", " ssl/statem/statem_srvr.c.", " - CVE-2024-2511", " * SECURITY UPDATE: checking excessively long DSA keys or params very slow", " - debian/patches/CVE-2024-4603.patch: check DSA parameters for", " excessive sizes before validating in crypto/dsa/dsa_check.c,", " test/recipes/15-test_dsaparam_data/invalid/p10240_q256_too_big.pem.", " - CVE-2024-4603", " * SECURITY UPDATE: use after free with SSL_free_buffers", " - debian/patches/CVE-2024-4741.patch: only free the read buffers if", " we're not using them in ssl/record/rec_layer_s3.c,", " ssl/record/record.h, ssl/ssl_lib.c.", " - CVE-2024-4741", " * SECURITY UPDATE: crash or memory disclosure via SSL_select_next_proto", " - debian/patches/CVE-2024-5535.patch: validate provided client list in", " ssl/ssl_lib.c.", " - CVE-2024-5535", "" ], "package": "openssl", "version": "3.0.13-0ubuntu3.2", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 30 Jul 2024 11:03:13 -0400" } ], "notes": null }, { "name": "python3.12", "from_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1", "version": "3.12.3-1" }, "to_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1ubuntu0.1", "version": "3.12.3-1ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: is_private and is_global mismatch", " - debian/patches/CVE-2024-4032.patch: fix \"private\" (non-global) IP", " address ranges in Doc/library/ipaddress.rst, Lib/ipaddress.py,", " Lib/test/test_ipaddress.py.", " - CVE-2024-4032", "" ], "package": "python3.12", "version": "3.12.3-1ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 31 Jul 2024 13:43:48 -0400" } ], "notes": null }, { "name": "python3.12-minimal", "from_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1", "version": "3.12.3-1" }, "to_version": { "source_package_name": "python3.12", "source_package_version": "3.12.3-1ubuntu0.1", "version": "3.12.3-1ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-4032", "url": "https://ubuntu.com/security/CVE-2024-4032", "cve_description": "The “ipaddress” module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as “globally reachable” or “private”. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn’t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries. CPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior.", "cve_priority": "low", "cve_public_date": "2024-06-17 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: is_private and is_global mismatch", " - debian/patches/CVE-2024-4032.patch: fix \"private\" (non-global) IP", " address ranges in Doc/library/ipaddress.rst, Lib/ipaddress.py,", " Lib/test/test_ipaddress.py.", " - CVE-2024-4032", "" ], "package": "python3.12", "version": "3.12.3-1ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 31 Jul 2024 13:43:48 -0400" } ], "notes": null }, { "name": "snapd", "from_version": { "source_package_name": "snapd", "source_package_version": "2.63+24.04", "version": "2.63+24.04" }, "to_version": { "source_package_name": "snapd", "source_package_version": "2.63+24.04ubuntu0.1", "version": "2.63+24.04ubuntu0.1" }, "cves": [ { "cve": "CVE-2024-1724", "url": "https://ubuntu.com/security/CVE-2024-1724", "cve_description": "In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which used the 'home' plug could use this vulnerability to install arbitrary scripts into the users PATH which may then be run by the user outside of the expected snap sandbox and hence allow them to escape confinement.", "cve_priority": "medium", "cve_public_date": "2024-07-25 19:15:00 UTC" }, { "cve": "CVE-2024-29068", "url": "https://ubuntu.com/security/CVE-2024-29068", "cve_description": "In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service.", "cve_priority": "medium", "cve_public_date": "2024-07-25 20:15:00 UTC" }, { "cve": "CVE-2024-29069", "url": "https://ubuntu.com/security/CVE-2024-29069", "cve_description": "In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.", "cve_priority": "medium", "cve_public_date": "2024-07-25 20:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-1724", "url": "https://ubuntu.com/security/CVE-2024-1724", "cve_description": "In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which used the 'home' plug could use this vulnerability to install arbitrary scripts into the users PATH which may then be run by the user outside of the expected snap sandbox and hence allow them to escape confinement.", "cve_priority": "medium", "cve_public_date": "2024-07-25 19:15:00 UTC" }, { "cve": "CVE-2024-29068", "url": "https://ubuntu.com/security/CVE-2024-29068", "cve_description": "In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service.", "cve_priority": "medium", "cve_public_date": "2024-07-25 20:15:00 UTC" }, { "cve": "CVE-2024-29069", "url": "https://ubuntu.com/security/CVE-2024-29069", "cve_description": "In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.", "cve_priority": "medium", "cve_public_date": "2024-07-25 20:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: sandbox escape via $HOME/bin", " - interfaces/builtin/home: explicitly deny writing to @{HOME}/bin", " - CVE-2024-1724", " * SECURITY UPDATE: denial-of-service via crafted files in squashfs image", " - snap, snapdir, squashfs: improve validation of target file", " mode/types", " - CVE-2024-29068", " * SECURITY UPDATE: information disclosure via crafted symlinks in", " squashfs image", " - snap, snapdir, squashfs: improve external symlink validation", " - CVE-2024-29069", "" ], "package": "snapd", "version": "2.63+24.04ubuntu0.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Alex Murray ", "date": "Fri, 26 Jul 2024 12:02:26 +0930" } ], "notes": null }, { "name": "thin-provisioning-tools", "from_version": { "source_package_name": "thin-provisioning-tools", "source_package_version": "0.9.0-2ubuntu5", "version": "0.9.0-2ubuntu5" }, "to_version": { "source_package_name": "thin-provisioning-tools", "source_package_version": "0.9.0-2ubuntu5.1", "version": "0.9.0-2ubuntu5.1" }, "cves": [], "launchpad_bugs_fixed": [ 2065180 ], "changes": [ { "cves": [], "log": [ "", " * initramfs-hook: Combine calls to manual_add_modules (LP: #2065180)", "" ], "package": "thin-provisioning-tools", "version": "0.9.0-2ubuntu5.1", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2065180 ], "author": "Benjamin Drung ", "date": "Mon, 01 Jul 2024 20:48:29 +0200" } ], "notes": null } ], "snap": [] }, "added": { "deb": [], "snap": [] }, "removed": { "deb": [], "snap": [] }, "notes": "Changelog diff for Ubuntu 24.04 noble image from release image serial 20240725 to 20240806", "from_series": "noble", "to_series": "noble", "from_serial": "20240725", "to_serial": "20240806", "from_manifest_filename": "release_manifest.previous", "to_manifest_filename": "manifest.current" }