{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-34824 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-34824 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-34824 is a high-severity vulnerability in n/a, published on 29 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-34824 and fix it if it is affected.\n\nWhat it is: CVE-2021-34824 is a high-severity vulnerability in n/a, published on 29 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-34824 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-2021-34824/ (Markdown: https://insights.sbomify.com/CVE-2021-34824/index.md)","id":"CVE-2021-34824","markdown":"https://insights.sbomify.com/CVE-2021-34824/index.md","name":"CVE-2021-34824","record":{"aliases":["GHSA-m879-9xpq-ppwc"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Istio service mesh","requires_auth":"low_privilege","summary":"Attackers can access credentials from different namespaces via Gateway and DestinationRule fields, exposing sensitive data in Istio service meshes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"istio","vendor":"istio"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Istio (1.8.x, 1.9.0-1.9.5 and 1.10.0-1.10.1) contains a remotely exploitable vulnerability where credentials specified in the Gateway and DestinationRule credentialName field can be accessed from different namespaces.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-12-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-12-23T18:19:06Z","kind":"github_poc","ref":"https://github.com/rsalmond/CVE-2021-34824","stars":0,"title":"reproducing an old istio bug"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2021-34824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2021-34825"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2021-34823"},"products":["n/a"],"published":"2021-06-29","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.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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can access credentials from different namespaces via Gateway and DestinationRule fields, exposing sensitive data in Istio service meshes.","url":"https://insights.sbomify.com/CVE-2021-34824/"}