@grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| grpc | grpc-node | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Grpc | Grpc-node |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-88h9-xgvx-hvf2 | @grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.251% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Grpc
Grpc grpc-node |
|
| Vendors & Products |
Grpc
Grpc grpc-node |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | @grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches | |
| Weaknesses | CWE-187 CWE-863 |
|
| References |
|
|
| Metrics |
cvssV3_1
|