{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2021-22017 in the wild since at least 10 Jan 2022.","fix":"No fix has been published for CVE-2021-22017 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Jan 2022.","what":"CVE-2021-22017 is a medium-severity vulnerability in Vmware Vcenter Server, published on 23 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-22017 and fix it if it is affected.\n\nWhat it is: CVE-2021-22017 is a medium-severity vulnerability in Vmware Vcenter Server, published on 23 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2021-22017 in the wild since at least 10 Jan 2022.\n\nAffected product: Vmware Vcenter Server. 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-22017/ (Markdown: https://insights.sbomify.com/CVE-2021-22017/index.md)","id":"CVE-2021-22017","markdown":"https://insights.sbomify.com/CVE-2021-22017/index.md","name":"CVE-2021-22017","record":{"aliases":["GHSA-w46j-w72r-9x98"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"VMware vCenter Server","requires_auth":"none","summary":"A network attacker can bypass proxy restrictions in vCenter Server to access internal endpoints due to improper URI normalization.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"vcenter_server","vendor":"vmware"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"Rhttproxy as used in vCenter Server contains a vulnerability due to improper implementation of URI normalization. A malicious actor with network access to port 443 on vCenter Server may exploit this issue to bypass proxy leading to internal endpoints being accessed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2021/CVE-2021-22017.yaml","stars":null,"title":"vCenter Server - Improper Access Control"}],"tier":"exploited"},"has_fix":null,"headline":"VMware vCenter Server Improper Access Control","id":"CVE-2021-22017","indexable":true,"kev":{"dateAdded":"2022-01-10","dueDate":"2022-01-24","knownRansomwareCampaignUse":"Unknown","product":"vCenter Server","requiredAction":"Apply updates per vendor instructions.","vendorProject":"VMware","vulnerabilityName":"VMware vCenter Server Improper Access Control"},"kind":"cve","links":{"ecosystem":null,"product":"vmware:vcenter_server","products":["vmware:vcenter_server"],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in VMware vCenter Server, VMware Cloud Foundation","id":"CVE-2021-22018"},"packages":[],"prev":{"headline":"Cross-site scripting in VMware vCenter Server, VMware Cloud Foundation","id":"CVE-2021-22016"},"products":["VMware vCenter Server, VMware Cloud Foundation"],"published":"2021-09-23","related":[{"cvss_score":9.8,"headline":"Broadcom VMware vCenter Path Traversal","id":"CVE-2026-59310","kev_date_added":"2026-08-18","published":"2026-07-30"},{"cvss_score":9.8,"headline":"VMware vCenter Server Out-of-Bounds Write","id":"CVE-2023-34048","kev_date_added":"2024-01-22","published":"2023-10-25"},{"cvss_score":9.8,"headline":"VMware vCenter Server Information Disclosure","id":"CVE-2020-3952","kev_date_added":"2021-11-03","published":"2020-04-10"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2015-2342","kev_date_added":null,"published":"2015-10-12"},{"cvss_score":9.8,"headline":"vCenter authentication-bypass vulnerability","id":"CVE-2026-59309","kev_date_added":null,"published":"2026-07-30"},{"cvss_score":9.8,"headline":"Memory corruption in VMware Cloud Foundation","id":"CVE-2024-37080","kev_date_added":null,"published":"2024-06-18"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"A network attacker can bypass proxy restrictions in vCenter Server to access internal endpoints due to improper URI normalization.","url":"https://insights.sbomify.com/CVE-2021-22017/"}