@grpc/grps-js: A malformed request can cause a server crash
- 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.9.16, 1.11.4, 1.12.7, 1.13.5, 1.14.4, and 1 more
- 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: yes
- Technical impact: partial
Summary
@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming HTTP/2 stream initiation can cause a server process created using @grpc/grpc-js to crash. This issue is fixed in versions 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- grpc grpc-node
fixed in 1.9.16; From 1.11.0 · fixed in 1.11.4; From 1.12.0 · fixed in 1.12.7; From 1.13.0 · fixed in 1.13.5; From 1.14.0 · fixed in 1.14.4; From 1.10.0 · fixed in 1.10.12
- @grpc/grpc-jsnpm
fixed in 1.9.16
- @grpc/grpc-jsnpm
From 1.10.0 · fixed in 1.10.12
- @grpc/grpc-jsnpm
From 1.11.0 · fixed in 1.11.4
- @grpc/grpc-jsnpm
From 1.12.0 · fixed in 1.12.7
- @grpc/grpc-jsnpm
From 1.13.0 · fixed in 1.13.5
- @grpc/grpc-jsnpm
From 1.14.0 · fixed in 1.14.4