{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12995 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12995 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12995 is a high-severity vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12995 and fix it if it is affected.\n\nWhat it is: CVE-2019-12995 is a high-severity vulnerability in n/a, published on 28 Jun 2019. 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-2019-12995 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-2019-12995/ (Markdown: https://insights.sbomify.com/CVE-2019-12995/index.md)","id":"CVE-2019-12995","markdown":"https://insights.sbomify.com/CVE-2019-12995/index.md","name":"CVE-2019-12995","record":{"aliases":["GHSA-45mv-99hf-m73p"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Istio service mesh","requires_auth":"none","summary":"Attackers can cause a segmentation fault in Envoy via mishandled access tokens, leading to service disruption in Istio deployments.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"istio","vendor":"istio"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"Istio before 1.2.2 mishandles certain access tokens, leading to \"Epoch 0 terminated with an error\" in Envoy. This is related to a jwt_authenticator.cc segmentation fault.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Null dereference in n/a","id":"CVE-2019-12995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"XML external entity in n/a","id":"CVE-2019-12996"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-12994"},"products":["n/a"],"published":"2019-06-28","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":"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 cause a segmentation fault in Envoy via mishandled access tokens, leading to service disruption in Istio deployments.","url":"https://insights.sbomify.com/CVE-2019-12995/"}