Information leak in gRPC
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.53.1, 1.54.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Google gRPC
From 1.53 · through 1.54
- grpcioPyPI
From 1.53.0 · fixed in 1.53.1; From 1.54.0 · fixed in 1.54.2
- io.grpc:grpc-protobufMaven
From 1.53.0 · fixed in 1.53.1
- grpcioPyPI
From 1.53.0 · fixed in 1.53.1
- grpcRubyGems
From 1.53.0 · fixed in 1.53.1
- grpcioPyPI
From 1.54.0 · fixed in 1.54.2
- grpcRubyGems
From 1.54.0 · fixed in 1.54.2
- io.grpc:grpc-protobufMaven
From 1.54.0 · fixed in 1.54.2