Описание
Security update for elemental-toolkit
This update for elemental-toolkit fixes the following issue
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260277).
Changes:
- Update to v2.3.4:
- 974af043 Bump golang.org/x/net to v0.55.0 (bsc#1267168 bsc#1251679)
- ae39c90f Bump golang.org/x/crypto to v0.52.0 (bsc#1266187)
- Update to v2.3.3:
- 8b4af274 Avoid pulling binaries with curl
- d46e30f4 Bump golangci/golangci-lint-action to v9
- 02caf200 Bump github.com/spf13/cobra library
- e29e1fbf Bump github.com/jaypipes/ghw library
- 652654e1 Bump github.com/bramvdbogaerde/go-scp library
- f94a0c58 Bump google.golang.org/grpc library (bsc#1260277 CVE-2026-33186)
- dc1a2056 Bump github.com/ulikunitz/xz library
- 337a986c Update headers to 2026
- d6aac085 Switch from TW to Leap 16.0 for green flavor
Список пакетов
openSUSE Leap 16.0
Ссылки
- SUSE Security Ratings
- SUSE Bug 1251679
- SUSE Bug 1260277
- SUSE Bug 1266187
- SUSE Bug 1267168
- SUSE CVE CVE-2026-33186 page
Описание
gRPC-Go is the Go language implementation of gRPC. Versions prior to 1.79.3 have an authorization bypass resulting from improper input validation of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. This affects gRPC-Go servers that use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`; AND that have a security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. The fix in version 1.79.3 ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: Use a validating interceptor (recommended mitigation); infrastructure-level normalization; and/or policy hardening.
Затронутые продукты
Ссылки
- CVE-2026-33186
- SUSE Bug 1260085