{"answers":{"affected":"1 open source package ship an affected version, including envoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32778 in the wild and no public exploit code.","fix":"Upgrade envoy to a fixed version for your release line: 1.16.5, 1.17.4, 1.18.4 or 1.19.1.","what":"CVE-2021-32778 is a medium-severity denial of service vulnerability in Envoyproxy Envoy, published on 24 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32778 and fix it if it is affected.\n\nWhat it is: CVE-2021-32778 is a medium-severity denial of service vulnerability in Envoyproxy Envoy, published on 24 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32778 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- envoy (Bitnami): affected from 1.16.0; fixed in 1.16.5, 1.17.4, 1.18.4, 1.19.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-32778/ (Markdown: https://insights.sbomify.com/CVE-2021-32778/index.md)","id":"CVE-2021-32778","markdown":"https://insights.sbomify.com/CVE-2021-32778/index.md","name":"CVE-2021-32778","record":{"aliases":["BIT-envoy-2021-32778","GHSA-3xh3-33v5-chcc","RHEA-2021:4051"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Envoy proxy","requires_auth":"none","summary":"Attackers can cause excessive CPU utilization and denial of service by resetting many HTTP/2 streams in Envoy proxy deployments with high stream limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"envoy","vendor":"envoyproxy"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-834","name":"Excessive Iteration"}],"description":"Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy’s procedure for resetting a HTTP/2 stream has O(N^2) complexity, leading to high CPU utilization when a large number of streams are reset. Deployments are susceptible to Denial of Service when Envoy is configured with high limit on H/2 concurrent streams. An attacker wishing to exploit this vulnerability would require a client opening and closing a large number of H/2 streams. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to reduce time complexity of resetting HTTP/2 streams. As a workaround users may limit the number of simultaneous HTTP/2 dreams for upstream and downstream peers to a low number, i.e. 100.","ecosystems":["Bitnami","Red Hat:service_mesh:2.1::el8"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Excessive CPU utilization when closing HTTP/2 streams","id":"CVE-2021-32778","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"denial_of_service","year":"2021"},"n_packages":14,"n_references":2,"next":{"headline":"Incorrectly handling of URI '#fragment' element as part of the path element","id":"CVE-2021-32779"},"packages":[{"ecosystem":"Bitnami","fixed":["1.16.5","1.17.4","1.18.4","1.19.1"],"introduced":["1.16.0","1.17.0","1.18.0","1.19.0"],"last_affected":[],"package":"envoy","purl":"pkg:bitnami/envoy","source":"BIT-envoy-2021-32778"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-5.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh","purl":"pkg:rpm/redhat/servicemesh","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-5.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-cni","purl":"pkg:rpm/redhat/servicemesh-cni","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:7.2.1-2.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-grafana","purl":"pkg:rpm/redhat/servicemesh-grafana","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:7.2.1-2.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-grafana-debuginfo","purl":"pkg:rpm/redhat/servicemesh-grafana-debuginfo","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-4.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-operator","purl":"pkg:rpm/redhat/servicemesh-operator","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-5.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-pilot-agent","purl":"pkg:rpm/redhat/servicemesh-pilot-agent","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-5.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-pilot-discovery","purl":"pkg:rpm/redhat/servicemesh-pilot-discovery","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.23.0-1.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-prometheus","purl":"pkg:rpm/redhat/servicemesh-prometheus","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-13.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy","purl":"pkg:rpm/redhat/servicemesh-proxy","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-13.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy-debuginfo","purl":"pkg:rpm/redhat/servicemesh-proxy-debuginfo","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-13.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy-debugsource","purl":"pkg:rpm/redhat/servicemesh-proxy-debugsource","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-13.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy-wasm","purl":"pkg:rpm/redhat/servicemesh-proxy-wasm","source":"RHEA-2021:4051"},{"ecosystem":"Red Hat:service_mesh:2.1::el8","fixed":["0:2.1.0-1.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-ratelimit","purl":"pkg:rpm/redhat/servicemesh-ratelimit","source":"RHEA-2021:4051"}],"prev":{"headline":"Incorrect concatenation of multiple value request headers in ext-authz extension","id":"CVE-2021-32777"},"products":["envoy"],"published":"2021-08-24","related":[{"cvss_score":10,"headline":"Trivial authentication bypass in Envoy","id":"CVE-2022-29226","kev_date_added":null,"published":"2022-06-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-18801","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-18802","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2020-35470","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.6,"headline":"Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata","id":"CVE-2024-23324","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":8.6,"headline":"Envoy vulnerable to OAuth2 credentials exploit with permanent validity","id":"CVE-2023-35941","kev_date_added":null,"published":"2023-07-25"},{"cvss_score":8.6,"headline":"Incorrect handling of H2 GOAWAY + SETTINGS frames","id":"CVE-2021-39162","kev_date_added":null,"published":"2021-09-09"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHEA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["envoyproxy"]},"summary":"Attackers can cause excessive CPU utilization and denial of service by resetting many HTTP/2 streams in Envoy proxy deployments with high stream limits.","url":"https://insights.sbomify.com/CVE-2021-32778/"}