@grpc/grpc-js vulnerabilities
gRPC Library for Node - pure JS implementation
- Registry
- npm
- Latest
- 1.14.6
- License
- Apache-2.0
6 known advisories
The latest version, 1.14.6, is not affected by any of them. Projects on older versions may be.
npm install @grpc/grpc-js@1.14.6Security advisories for @grpc/grpc-js
@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized
- Affected
- <1.13.6 · >=1.14.0 <1.14.5
- Fixed in
- 1.13.6, 1.14.5
@grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages
- Affected
- <1.13.6 · >=1.14.0 <1.14.5
- Fixed in
- 1.13.6, 1.14.5
@grpc/grpc-js: A malformed request can cause a server crash
- Affected
- <1.9.16 · >=1.10.0 <1.10.12 · >=1.11.0 <1.11.4 · >=1.12.0 <1.12.7 · >=1.13.0 <1.13.5 · >=1.14.0 <1.14.4
- Fixed in
- 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4
@grpc/grpc-js: An incoming malformed compressed message can cause a client or server crash
- Affected
- <1.9.16 · >=1.10.0 <1.10.12 · >=1.11.0 <1.11.4 · >=1.12.0 <1.12.7 · >=1.13.0 <1.13.5 · >=1.14.0 <1.14.4
- Fixed in
- 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, 1.14.4
@grpc/grpc-js can allocate memory for incoming messages well above configured limits
- Affected
- >=1.10.0 <1.10.9 · >=1.9.0 <1.9.15 · <1.8.22
- Fixed in
- 1.8.22, 1.9.15, 1.10.9
Prototype pollution in grpc and @grpc/grpc-js
- Affected
- <1.1.8
- Fixed in
- 1.1.8
Which of your client projects still run an old @grpc/grpc-js?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.