{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-8595 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-8595 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 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-8595 and fix it if it is affected.\n\nWhat it is: CVE-2020-8595 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 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-8595 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-8595/ (Markdown: https://insights.sbomify.com/CVE-2020-8595/index.md)","id":"CVE-2020-8595","markdown":"https://insights.sbomify.com/CVE-2020-8595/index.md","name":"CVE-2020-8595","record":{"aliases":["GHSA-6mcc-fxc5-58cv","RHSA-2020:0477"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Istio service mesh","requires_auth":"none","summary":"Attackers can bypass JWT authentication in Istio by appending special characters to URIs, gaining unauthorized access to protected HTTP paths.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"istio","vendor":"istio"},{"product":"openshift_service_mesh","vendor":"redhat"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Istio versions 1.2.10 (End of Life) and prior, 1.3 through 1.3.7, and 1.4 through 1.4.3 allows authentication bypass. The Authentication Policy exact-path matching logic can allow unauthorized access to HTTP paths even if they are configured to be only accessed after presenting a valid JWT token. For example, an attacker can add a ? or # character to a URI that would otherwise satisfy an exact-path match.","ecosystems":["Red Hat:service_mesh:1.0::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":"Auth bypass in n/a","id":"CVE-2020-8595","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":1,"n_references":6,"next":{"headline":"SQL injection in n/a","id":"CVE-2020-8596"},"packages":[{"ecosystem":"Red Hat:service_mesh:1.0::el8","fixed":["0:1.0.7-1.el8"],"introduced":["0"],"last_affected":[],"package":"servicemesh-proxy","purl":"pkg:rpm/redhat/servicemesh-proxy","source":"RHSA-2020:0477"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-8594"},"products":["n/a"],"published":"2020-02-12","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-31921","kev_date_added":null,"published":"2021-06-02"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2021-34824","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":8.7,"headline":"Istio JWKS resolver to prevent private key material from being exposed when JWKS fetch fails.","id":"CVE-2026-31837","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":8.3,"headline":"Authorization Policy Bypass Due to Case Insensitive Host Comparison","id":"CVE-2021-39155","kev_date_added":null,"published":"2021-08-24"},{"cvss_score":8.1,"headline":"Fragments in Path May Lead to Authorization Policy Bypass","id":"CVE-2021-39156","kev_date_added":null,"published":"2021-08-24"},{"cvss_score":7.6,"headline":"Istio may allow identity impersonation if user has localhost access","id":"CVE-2022-39388","kev_date_added":null,"published":"2022-11-10"},{"cvss_score":7.5,"headline":"Istio vulnerable to denial of service attack due to Golang Regex Library","id":"CVE-2022-39278","kev_date_added":null,"published":"2022-10-13"}],"sources":[{"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":"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-04","vendors":["n/a"]},"summary":"Attackers can bypass JWT authentication in Istio by appending special characters to URIs, gaining unauthorized access to protected HTTP paths.","url":"https://insights.sbomify.com/CVE-2020-8595/"}