Red Hat Run Once Duration Override Operator
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Red Hat Run Once Duration Override Operator.
Recent Red Hat Run Once Duration Override Operator Security Advisories
| Advisory | Title | Published |
|---|---|---|
| RHSA-2024:8337 | (RHSA-2024:8337) Moderate: Run Once Duration Override Operator for Red Hat OpenShift 1.1.2 for RHEL 9 | October 31, 2024 |
| RHSA-2024:7548 | (RHSA-2024:7548) Moderate: Run Once Duration Override Operator for Red Hat OpenShift 1.2.0 for RHEL 9 | October 16, 2024 |
| RHSA-2024:1616 | (RHSA-2024:1616) Important: Run Once Duration Override Operator for Red Hat OpenShift 1.1.1 for RHEL 9 | July 1, 2024 |
| RHSA-2024:0269 | (RHSA-2024:0269) Moderate: Run Once Duration Override Operator for Red Hat OpenShift 1.1.0 for RHEL 9 | February 28, 2024 |
| RHSA-2023:5947 | (RHSA-2023:5947) Important: Run Once Duration Override Operator for Red Hat OpenShift 1.0.1 security update | October 26, 2023 |
By the Year
In 2026 there have been 1 vulnerability in Red Hat Run Once Duration Override Operator with an average score of 9.1 out of ten. Run Once Duration Override Operator did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2026 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 1 | 9.10 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 1 | 7.50 |
It may take a day or so for new Run Once Duration Override Operator vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Red Hat Run Once Duration Override Operator Security Vulnerabilities
gRPC-Go Auth Bypass (1.79.2) via noncanonical :path
CVE-2026-33186
9.1 - Critical
- March 20, 2026
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.
AuthZ
HTTP/2 DoS via Stream Reset in nginx
CVE-2023-44487
7.5 - High
- October 10, 2023
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
Resource Exhaustion
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Red Hat Run Once Duration Override Operator or by Red Hat? Click the Watch button to subscribe.
