Skip to content

gRPC Reachable Assertion issue

High severity GitHub Reviewed Published Jul 6, 2023 to the GitHub Advisory Database • Updated Nov 10, 2023

Package

bundler grpc (RubyGems)

Affected versions

< 1.53.0

Patched versions

1.53.0
pip grpcio (pip)
< 1.53.0
1.53.0
maven io.grpc:grpc-protobuf (Maven)
< 1.53.0
1.53.0

Description

There exists an vulnerability causing an abort() to be called in gRPC. 
The following headers cause gRPC's C++ implementation to abort() when called via http2:

te: x (x != trailers)

:scheme: x (x != http, https)

grpclb_client_stats: x (x == anything)

On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.

References

Published by the National Vulnerability Database Jun 9, 2023
Published to the GitHub Advisory Database Jul 6, 2023
Reviewed Jul 6, 2023
Last updated Nov 10, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.111%
(46th percentile)

Weaknesses

CVE ID

CVE-2023-1428

GHSA ID

GHSA-6628-q6j9-w8vg

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.