{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2011-1789 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-1789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-1789 is a medium-severity vulnerability in Vmware Esx, published on 9 May 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2011-1789 and fix it if it is affected.\n\nWhat it is: CVE-2011-1789 is a medium-severity vulnerability in Vmware Esx, published on 9 May 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2011-1789 in the wild and no public exploit code.\n\nAffected product: Vmware Esx. 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-2011-1789/ (Markdown: https://insights.sbomify.com/CVE-2011-1789/index.md)","id":"CVE-2011-1789","markdown":"https://insights.sbomify.com/CVE-2011-1789/index.md","name":"CVE-2011-1789","record":{"aliases":["GHSA-3qx7-92qm-xvhr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VMware vSphere Client","requires_auth":"none","summary":"Attackers can distribute Trojan horse installers because the vSphere Client installer lacks a digital signature, requiring user interaction to execute.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"esx","vendor":"vmware"},{"product":"esxi","vendor":"vmware"},{"product":"vcenter","vendor":"vmware"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The self-extracting installer in the vSphere Client Installer package in VMware vCenter 4.0 before Update 3 and 4.1 before Update 1, VMware ESXi 4.x before 4.1 Update 1, and VMware ESX 4.x before 4.1 Update 1 does not have a digital signature, which might make it easier for remote attackers to spoof the software distribution via a Trojan horse installer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Supply chain in n/a","id":"CVE-2011-1789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vmware:esx","products":["vmware:esx","vmware:esxi"],"type":"supply_chain","year":"2011"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in n/a","id":"CVE-2011-1793"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2011-1788"},"products":["n/a"],"published":"2011-05-09","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2013-1405","kev_date_added":null,"published":"2013-02-15"},{"cvss_score":9.9,"headline":"Memory corruption in n/a","id":"CVE-2012-1516","kev_date_added":null,"published":"2012-05-04"},{"cvss_score":9.4,"headline":"Path traversal in n/a","id":"CVE-2013-3658","kev_date_added":null,"published":"2013-09-10"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2012-3288","kev_date_added":null,"published":"2012-06-14"},{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2008-4281","kev_date_added":null,"published":"2008-11-10"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2012-1517","kev_date_added":null,"published":"2012-05-04"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2012-2449","kev_date_added":null,"published":"2012-05-04"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can distribute Trojan horse installers because the vSphere Client installer lacks a digital signature, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2011-1789/"}