{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21701 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-21701 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21701 is a medium-severity vulnerability in istio, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21701 and fix it if it is affected.\n\nWhat it is: CVE-2022-21701 is a medium-severity vulnerability in istio, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-21701 in the wild and no public exploit code.\n\nAffected product: istio. 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-2022-21701/ (Markdown: https://insights.sbomify.com/CVE-2022-21701/index.md)","id":"CVE-2022-21701","markdown":"https://insights.sbomify.com/CVE-2022-21701/index.md","name":"CVE-2022-21701","record":{"aliases":["GHSA-mq8f-9446-c28r"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Istio service mesh","requires_auth":"low_privilege","summary":"Users with CREATE permissions on Gateway API objects can escalate privileges to create unauthorized resources like Pods in Istio.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"istio","vendor":"istio"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Istio is an open platform to connect, manage, and secure microservices. In versions 1.12.0 and 1.12.1 Istio is vulnerable to a privilege escalation attack. Users who have `CREATE` permission for `gateways.gateway.networking.k8s.io` objects can escalate this privilege to create other resources that they may not have access to, such as `Pod`. This vulnerability impacts only an Alpha level feature, the Kubernetes Gateway API. This is not the same as the Istio Gateway type (gateways.networking.istio.io), which is not vulnerable. Users are advised to upgrade to resolve this issue. Users unable to upgrade should implement any of the following which will prevent this vulnerability: Remove the gateways.gateway.networking.k8s.io CustomResourceDefinition, set PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER=true environment variable in Istiod, or remove CREATE permissions for gateways.gateway.networking.k8s.io objects from untrusted users.","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":"Privileged Escalation in Istio","id":"CVE-2022-21701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross site scripting in Grafana proxy","id":"CVE-2022-21702"},"packages":[],"prev":{"headline":"Memory leak in micronaut-core","id":"CVE-2022-21700"},"products":["istio"],"published":"2022-01-19","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["istio"]},"summary":"Users with CREATE permissions on Gateway API objects can escalate privileges to create unauthorized resources like Pods in Istio.","url":"https://insights.sbomify.com/CVE-2022-21701/"}