| Summary | 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. |
|---|---|
| Publication Date | Aug. 6, 2024, 8:16 p.m. |
| Registration Date | Aug. 7, 2024, 5:01 a.m. |
| Last Update | Aug. 7, 2024, 1:30 a.m. |
| Title | gRPC における脆弱性 |
|---|---|
| Summary | gRPC には、不特定の脆弱性が存在します。 |
| Possible impacts | 情報を取得される可能性があります。 |
| Solution | ベンダアドバイザリまたはパッチ情報が公開されています。参考情報を参照して適切な対策を実施してください。 |
| Publication Date | Aug. 6, 2024, midnight |
| Registration Date | July 23, 2025, 12:31 p.m. |
| Last Update | July 23, 2025, 12:31 p.m. |
| gRPC |
| gRPC 1.58.3 未満 |
| gRPC 1.59.0 以上 1.59.5 未満 |
| gRPC 1.60.0 以上 1.60.2 未満 |
| gRPC 1.61.0 以上 1.61.3 未満 |
| gRPC 1.62.0 以上 1.62.3 未満 |
| gRPC 1.63.0 以上 1.63.2 未満 |
| gRPC 1.64.0 以上 1.64.3 未満 |
| gRPC 1.65.0 以上 1.65.4 未満 |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2025年07月23日] 掲載 |
July 23, 2025, 12:31 p.m. |