CVE-2023-32731
Grpc 1.53.0 – 1.55.0
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:HSummary
CVE-2023-32731 is a high-severity Expected Behavior Violation (CWE-440) vulnerability in Grpc Grpc. Its CVSS base score is 7.4 (High).
Operationally, ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2030
Vulnerability Data
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.…
more
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
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Verification of security function operation directly detects deviations from expected behavior.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce specification compliance and catch expected-behavior violations during development.
Security testing and exercises help discover behavior deviations before deployment.
Vulnerability identification can surface spec-violating flaws, while eliminating the weakness reduces some vulnerability backlog.
Routine software maintenance and patching can remediate discovered specification violations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance validates that functions behave as specified.
Secure development life cycle mandates verification against specifications, directly reducing expected-behavior violations.
Application security requirements explicitly define expected behavior that must be met.
Secure coding practices enforce adherence to functional specifications during implementation.
Change management can catch specification deviations introduced by modifications.
Documented operating procedures reduce the chance that functions deviate from intended behavior.