@grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches

Why it is Yellow

• CVSS 6.5 medium
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-88h9-xgvx-hvf2
• https://github.com/grpc/grpc-node/security/advisories/GHSA-88h9-xgvx-hvf2
• https://github.com/grpc/grpc-node/commit/6cf64b596da03f1942a6b168998f0670217a99c4
• https://github.com/grpc/grpc-node/commit/a6c5b31180cc8cea94d0a5ea215ce31a49e0409f
• https://github.com/grpc/grpc-node/commit/f32f3712e44581d8dfc8359bd8d30096662f4c75
• https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds%401.13.1
• https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds%401.14.1
• https://github.com/advisories/GHSA-88h9-xgvx-hvf2

Original description

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.1 and 1.14.1, the exact path (method name) matcher used by RBAC performs a prefix comparison instead of an equality comparison when case-insensitive matching is enabled. If one service method name prefixes another and the methods have different access rules, a request for the longer method can match the shorter method's rule and cause incorrect authorization. This issue is fixed in versions 1.13.1 and 1.14.1.