REDHAT-BUG-2577566: High severity Solo.io kgateway vulnerability
When a TokenRateLimitPolicy is applied alongside an AuthPolicy on the same HTTPRoute, unauthenticated requests unexpectedly return HTTP 200 instead of 401 and reach the backend. The same failure occurs when a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of a route carrying a TokenRateLimitPolicy. Configured rate limits (5/min and 10/min) are not enforced, even with a burst of 30 requests. Removing the TokenRateLimitPolicy restores the expected authentication behavior, while a regular request-based RateLimitPolicy correctly enforces both authentication (401) and rate limiting (429).
Gateway logs show Limitador response JSON parsing and CEL predicate evaluation errors. The suspected root cause is that a response-body store action prepended to the WASM action chain cannot settle during the request phase, leaving the authentication guard pending and preventing the auth check from being dispatched.
Affected Software
Event History
Frequently Asked Questions
Which configurations are affected?
The issue occurs when a TokenRateLimitPolicy and an AuthPolicy are applied to the same HTTPRoute. It also occurs when a route with a TokenRateLimitPolicy is served by a Gateway or listener that has a RateLimitPolicy with defaults or overrides.
What is the practical security impact?
Unauthenticated requests can receive HTTP 200 and reach the backend instead of being rejected with HTTP 401. Configured token rate limits, including 5/min and 10/min limits, may also fail to enforce during a burst of requests.
How can I tell whether this issue is occurring?
Test an unauthenticated request to an affected route and check whether it returns HTTP 200 or reaches the backend rather than returning HTTP 401. Gateway logs may contain Limitador response JSON parsing errors and CEL predicate evaluation errors.
What mitigation is available if the affected policy combination cannot be patched immediately?
Removing the TokenRateLimitPolicy restores the expected authentication behavior. A regular request-based RateLimitPolicy correctly enforces authentication with HTTP 401 and rate limiting with HTTP 429.