5.3 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): High (H)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): None (N)
- Integrity (I): None (N)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): High (H)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): None (N)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): None (N)
- Modified Availability (MA): High (H)
by @mweinelt Activity log
- Created suggestion
-
@mweinelt
ignored
11 packages
- opa-envoy-plugin
- python312Packages.envoy-utils
- python313Packages.envoy-utils
- python314Packages.envoy-utils
- python312Packages.envoy-reader
- python313Packages.envoy-reader
- python314Packages.envoy-reader
- python313Packages.envoy-data-plane
- python314Packages.envoy-data-plane
- home-assistant-component-tests.enphase_envoy
- tests.home-assistant-component-tests.enphase_envoy
- @mweinelt accepted
- @mweinelt published on GitHub
Envoy global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, At the rate limit filter, if the response phase limit with apply_on_stream_done in the rate limit configuration is enabled and the response phase limit request fails directly, it may crash Envoy. When both the request phase limit and response phase limit are enabled, the safe gRPC client instance will be re-used for both the request phase request and response phase request. But after the request phase request is done, the inner state of the request phase limit request in gRPC client is not cleaned up. When a second limit request is sent at response phase, and the second limit request fails directly, the previous request's inner state may be accessed and result in crash. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.
References
-
https://github.com/envoyproxy/envoy/security/advisories/GHSA-c23c-rp3m-vpg3 x_refsource_CONFIRM
Affected products
- ==>= 1.36.0, < 1.36.5
- ==< 1.34.13
- ==>= 1.37.0, < 1.37.1
- ==>= 1.35.0, < 1.35.9
Matching in nixpkgs
Ignored packages (11)
pkgs.opa-envoy-plugin
Plugin to enforce OPA policies with Envoy
-
nixos-unstable 1.13.2-envoy-2
- nixpkgs-unstable 1.13.2-envoy-2
- nixos-unstable-small 1.13.2-envoy-2
pkgs.python312Packages.envoy-utils
None
pkgs.python313Packages.envoy-utils
Python utilities for the Enphase Envoy
pkgs.python314Packages.envoy-utils
Python utilities for the Enphase Envoy
pkgs.python312Packages.envoy-reader
None
pkgs.python313Packages.envoy-reader
Python module to read from Enphase Envoy units
pkgs.python314Packages.envoy-reader
Python module to read from Enphase Envoy units
pkgs.python313Packages.envoy-data-plane
Python dataclasses for the Envoy Data-Plane-API
pkgs.python314Packages.envoy-data-plane
Python dataclasses for the Envoy Data-Plane-API
pkgs.tests.home-assistant-component-tests.enphase_envoy
Open source home automation that puts local control and privacy first
Package maintainers
-
@lukegb Luke Granger-Brown <nix@lukegb.com>
-
@katexochen Paul Meyer <katexochen0@gmail.com>