{ "summary": { "snap": { "added": [], "removed": [], "diff": [ "lxd" ] }, "deb": { "added": [], "removed": [], "diff": [ "libpython3.8:s390x", "libpython3.8-minimal:s390x", "libpython3.8-stdlib:s390x", "libssl1.1:s390x", "openssl", "python3.8", "python3.8-minimal" ] } }, "diff": { "deb": [ { "name": "libpython3.8:s390x", "from_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.10", "version": "3.8.10-0ubuntu1~20.04.10" }, "to_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.11", "version": "3.8.10-0ubuntu1~20.04.11" }, "cves": [ { "cve": "CVE-2024-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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: race condition in ssl.SSLContext methods", " - debian/patches/CVE-2024-0397.patch: fix locking in cert_store_stats", " and get_ca_certs in Modules/_ssl.c.", " - CVE-2024-0397", " * 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.8", "version": "3.8.10-0ubuntu1~20.04.11", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jul 2024 13:02:10 -0400" } ], "notes": null }, { "name": "libpython3.8-minimal:s390x", "from_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.10", "version": "3.8.10-0ubuntu1~20.04.10" }, "to_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.11", "version": "3.8.10-0ubuntu1~20.04.11" }, "cves": [ { "cve": "CVE-2024-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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: race condition in ssl.SSLContext methods", " - debian/patches/CVE-2024-0397.patch: fix locking in cert_store_stats", " and get_ca_certs in Modules/_ssl.c.", " - CVE-2024-0397", " * 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.8", "version": "3.8.10-0ubuntu1~20.04.11", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jul 2024 13:02:10 -0400" } ], "notes": null }, { "name": "libpython3.8-stdlib:s390x", "from_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.10", "version": "3.8.10-0ubuntu1~20.04.10" }, "to_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.11", "version": "3.8.10-0ubuntu1~20.04.11" }, "cves": [ { "cve": "CVE-2024-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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: race condition in ssl.SSLContext methods", " - debian/patches/CVE-2024-0397.patch: fix locking in cert_store_stats", " and get_ca_certs in Modules/_ssl.c.", " - CVE-2024-0397", " * 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.8", "version": "3.8.10-0ubuntu1~20.04.11", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jul 2024 13:02:10 -0400" } ], "notes": null }, { "name": "libssl1.1:s390x", "from_version": { "source_package_name": "openssl", "source_package_version": "1.1.1f-1ubuntu2.22", "version": "1.1.1f-1ubuntu2.22" }, "to_version": { "source_package_name": "openssl", "source_package_version": "1.1.1f-1ubuntu2.23", "version": "1.1.1f-1ubuntu2.23" }, "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-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-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: 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": "1.1.1f-1ubuntu2.23", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 30 Jul 2024 12:36:54 -0400" } ], "notes": null }, { "name": "openssl", "from_version": { "source_package_name": "openssl", "source_package_version": "1.1.1f-1ubuntu2.22", "version": "1.1.1f-1ubuntu2.22" }, "to_version": { "source_package_name": "openssl", "source_package_version": "1.1.1f-1ubuntu2.23", "version": "1.1.1f-1ubuntu2.23" }, "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-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-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: 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": "1.1.1f-1ubuntu2.23", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 30 Jul 2024 12:36:54 -0400" } ], "notes": null }, { "name": "python3.8", "from_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.10", "version": "3.8.10-0ubuntu1~20.04.10" }, "to_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.11", "version": "3.8.10-0ubuntu1~20.04.11" }, "cves": [ { "cve": "CVE-2024-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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: race condition in ssl.SSLContext methods", " - debian/patches/CVE-2024-0397.patch: fix locking in cert_store_stats", " and get_ca_certs in Modules/_ssl.c.", " - CVE-2024-0397", " * 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.8", "version": "3.8.10-0ubuntu1~20.04.11", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jul 2024 13:02:10 -0400" } ], "notes": null }, { "name": "python3.8-minimal", "from_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.10", "version": "3.8.10-0ubuntu1~20.04.10" }, "to_version": { "source_package_name": "python3.8", "source_package_version": "3.8.10-0ubuntu1~20.04.11", "version": "3.8.10-0ubuntu1~20.04.11" }, "cves": [ { "cve": "CVE-2024-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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-0397", "url": "https://ubuntu.com/security/CVE-2024-0397", "cve_description": "A defect was discovered in the Python “ssl” module where there is a memory race condition with the ssl.SSLContext methods “cert_store_stats()” and “get_ca_certs()”. The race condition can be triggered if the methods are called at the same time as certificates are loaded into the SSLContext, such as during the TLS handshake with a certificate directory configured. This issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5.", "cve_priority": "medium", "cve_public_date": "2024-06-17 16:15:00 UTC" }, { "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: race condition in ssl.SSLContext methods", " - debian/patches/CVE-2024-0397.patch: fix locking in cert_store_stats", " and get_ca_certs in Modules/_ssl.c.", " - CVE-2024-0397", " * 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.8", "version": "3.8.10-0ubuntu1~20.04.11", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jul 2024 13:02:10 -0400" } ], "notes": null } ], "snap": [ { "name": "lxd", "from_version": { "source_package_name": null, "source_package_version": null, "version": "24063" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": "29628" } } ] }, "added": { "deb": [], "snap": [] }, "removed": { "deb": [], "snap": [] }, "notes": "Changelog diff for Ubuntu 20.04 focal image from release image serial 20240725 to 20240731", "from_series": "focal", "to_series": "focal", "from_serial": "20240725", "to_serial": "20240731", "from_manifest_filename": "release_manifest.previous", "to_manifest_filename": "manifest.current" }