From 4b9e8de50e10b50d429890a22e0bc84c66308778 Mon Sep 17 00:00:00 2001 From: Lin Sun Date: Thu, 14 Nov 2019 15:45:46 -0500 Subject: [PATCH] small clarification (#5688) we got users asking us if this config can be removed so add a comment here to clarify it. --- content/en/news/2019/announcing-1.3.5/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/news/2019/announcing-1.3.5/index.md b/content/en/news/2019/announcing-1.3.5/index.md index a9c4acd9ea..3f0bbbd277 100644 --- a/content/en/news/2019/announcing-1.3.5/index.md +++ b/content/en/news/2019/announcing-1.3.5/index.md @@ -17,7 +17,7 @@ This release contains fixes for the security vulnerability described in [our Nov - **ISTIO-SECURITY-2019-006** A DoS vulnerability has been discovered in Envoy. -__[CVE-2019-18817](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18817)__: An infinite loop can be triggered in Envoy if the option `continue_on_listener_filters_timeout` is set to True, which is the case in Istio. This vulnerability could be leveraged for a DoS attack. +__[CVE-2019-18817](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18817)__: An infinite loop can be triggered in Envoy if the option `continue_on_listener_filters_timeout` is set to True, which is the case in Istio. This vulnerability could be leveraged for a DoS attack. If you applied the mitigation mentioned in [our November 11, 2019 news post](/news/2019/istio-security-2019-006), you can remove the mitigation once you upgrade to Istio 1.3.5 or newer. ## Bug fixes