An update for grpc is now available for openEuler-24.03-LTS Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2024-2064 Final 1.0 1.0 2024-08-30 Initial 2024-08-30 2024-08-30 openEuler SA Tool V1.0 2024-08-30 grpc security update An update for grpc is now available for openEuler-24.03-LTS gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. Security Fix(es): It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values. This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table. Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.(CVE-2024-7246) An update for grpc is now available for openEuler-24.03-LTS. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium grpc https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2064 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2024-7246 https://nvd.nist.gov/vuln/detail/CVE-2024-7246 openEuler-24.03-LTS grpc-1.60.0-4.oe2403.x86_64.rpm grpc-debuginfo-1.60.0-4.oe2403.x86_64.rpm grpc-debugsource-1.60.0-4.oe2403.x86_64.rpm grpc-devel-1.60.0-4.oe2403.x86_64.rpm grpc-plugins-1.60.0-4.oe2403.x86_64.rpm python3-grpcio-1.60.0-4.oe2403.x86_64.rpm grpc-1.60.0-4.oe2403.aarch64.rpm grpc-debuginfo-1.60.0-4.oe2403.aarch64.rpm grpc-debugsource-1.60.0-4.oe2403.aarch64.rpm grpc-devel-1.60.0-4.oe2403.aarch64.rpm grpc-plugins-1.60.0-4.oe2403.aarch64.rpm python3-grpcio-1.60.0-4.oe2403.aarch64.rpm grpc-1.60.0-4.oe2403.src.rpm It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values. This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table. Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4. 2024-08-30 CVE-2024-7246 openEuler-24.03-LTS Medium 5.8 AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L grpc security update 2024-08-30 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2064