@grpc/grpc-js: safe_regex incorrectly applies partial string matching for patterns with alternation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in @grpc/grpc-js-xds 1.13.2 and @grpc/grpc-js-xds 1.14.2.
@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Before 1.13.2, and from 1.14.0 through 1.14.1, the @grpc/grpc-js-xds SafeRegexValueMatcher and PathSafeRegexValueMatcher add start and end anchors without grouping a supplied top-level alternation. An expression intended to match one of several complete values can therefore match a prefix, substring, or suffix. The affected matchers are used for route selection, xDS credential identity matching, and RBAC URL path, principal name, server name, and header rules. An ALLOW policy using an alternation can consequently accept a method, certificate identity, or header value outside the intended set, while a DENY policy becomes broader rather than permissive. This issue is fixed in versions 1.13.2 and 1.14.2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| grpc | <1.13.2, >=1.14.0 <1.14.2 | ||
| npm: @grpc/grpc-js-xds | <1.13.2, >=1.14.0 <1.14.2 | 1.13.2, 1.14.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in @grpc/grpc-js-xds (npm), strongest first
Embed
A live severity badge for an advisory, README or ticket