{"answers":{"affected":"1 open source package ship an affected version, including envoy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25017 in the wild and no public exploit code.","fix":"Upgrade envoy to a fixed version for your release line: 1.12.7, 1.13.4, 1.14.4 or 1.15.1.","what":"CVE-2020-25017 is a high-severity vulnerability in Envoyproxy Envoy, published on 1 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25017 and fix it if it is affected.\n\nWhat it is: CVE-2020-25017 is a high-severity vulnerability in Envoyproxy Envoy, published on 1 Oct 2020. 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-2020-25017 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- envoy (Bitnami): affected all versions; fixed in 1.12.7, 1.13.4, 1.14.4, 1.15.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-2020-25017/ (Markdown: https://insights.sbomify.com/CVE-2020-25017/index.md)","id":"CVE-2020-25017","markdown":"https://insights.sbomify.com/CVE-2020-25017/index.md","name":"CVE-2020-25017","record":{"aliases":["BIT-envoy-2020-25017","GHSA-2v25-cjjq-5f4w","RHSA-2020:4129"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Envoy proxy","requires_auth":"none","summary":"Envoy proxy fails to replace all header values, potentially allowing attackers to bypass security controls relying on header inspection.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"envoy","vendor":"envoyproxy"}],"cvss":{"score":8.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[],"description":"Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.","ecosystems":["Bitnami","Red Hat:service_mesh:1.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":"Other in n/a","id":"CVE-2020-25017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"envoyproxy:envoy","products":["envoyproxy:envoy"],"type":"other","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2020-25018"},"packages":[{"ecosystem":"Bitnami","fixed":["1.12.7","1.13.4","1.14.4","1.15.1"],"introduced":["0","1.13.0","1.14.0","1.15.0"],"last_affected":[],"package":"envoy","purl":"pkg:bitnami/envoy","source":"BIT-envoy-2020-25017"},{"ecosystem":"Red Hat:service_mesh:1.1::el8","fixed":["0:1.1.9-1.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy","purl":"pkg:rpm/redhat/servicemesh-proxy","source":"RHSA-2020:4129"}],"prev":{"headline":"Out of bounds access in rgb","id":"CVE-2020-25016"},"products":["n/a"],"published":"2020-10-01","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":"RHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Envoy proxy fails to replace all header values, potentially allowing attackers to bypass security controls relying on header inspection.","url":"https://insights.sbomify.com/CVE-2020-25017/"}