{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-1775 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2011-1775 is a medium-severity vulnerability in n/a, published on 26 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-1775 and fix it if it is affected.\n\nWhat it is: CVE-2011-1775 is a medium-severity vulnerability in n/a, published on 26 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-1775 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-2011-1775/ (Markdown: https://insights.sbomify.com/CVE-2011-1775/index.md)","id":"CVE-2011-1775","markdown":"https://insights.sbomify.com/CVE-2011-1775/index.md","name":"CVE-2011-1775","record":{"aliases":["GHSA-g8f8-5m52-5p35","RHSA-2011:0871"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC client","requires_auth":"none","summary":"Man-in-the-middle attackers can spoof TLS VNC servers by bypassing X.509 certificate verification in the TigerVNC client.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tigervnc","vendor":"tigervnc"}],"cvss":{"score":5.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The CSecurityTLS::processMsg function in common/rfb/CSecurityTLS.cxx in the vncviewer component in TigerVNC 1.1beta1 does not properly verify the server's X.509 certificate, which allows man-in-the-middle attackers to spoof a TLS VNC server via an arbitrary certificate.","ecosystems":["Red Hat:enterprise_linux:6::server"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2011-1775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2011"},"n_packages":5,"n_references":11,"next":{"headline":"Memory corruption in n/a","id":"CVE-2011-1776"},"packages":[{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["0:1.0.90-0.15.20110314svn4359.el6_1.1"],"introduced":["0"],"last_affected":[],"package":"tigervnc","purl":"pkg:rpm/redhat/tigervnc","source":"RHSA-2011:0871"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["0:1.0.90-0.15.20110314svn4359.el6_1.1"],"introduced":["0"],"last_affected":[],"package":"tigervnc-debuginfo","purl":"pkg:rpm/redhat/tigervnc-debuginfo","source":"RHSA-2011:0871"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["0:1.0.90-0.15.20110314svn4359.el6_1.1"],"introduced":["0"],"last_affected":[],"package":"tigervnc-server","purl":"pkg:rpm/redhat/tigervnc-server","source":"RHSA-2011:0871"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["0:1.0.90-0.15.20110314svn4359.el6_1.1"],"introduced":["0"],"last_affected":[],"package":"tigervnc-server-applet","purl":"pkg:rpm/redhat/tigervnc-server-applet","source":"RHSA-2011:0871"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["0:1.0.90-0.15.20110314svn4359.el6_1.1"],"introduced":["0"],"last_affected":[],"package":"tigervnc-server-module","purl":"pkg:rpm/redhat/tigervnc-server-module","source":"RHSA-2011:0871"}],"prev":{"headline":"File upload in n/a","id":"CVE-2011-1774"},"products":["n/a"],"published":"2011-05-26","related":[{"cvss_score":9.8,"headline":"Memory corruption in TigerVNC","id":"CVE-2014-0011","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-5581","kev_date_added":null,"published":"2017-02-28"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2017-7393","kev_date_added":null,"published":"2017-04-01"},{"cvss_score":8.5,"headline":"Missing authorization in TigerVNC","id":"CVE-2026-34352","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7392","kev_date_added":null,"published":"2017-04-01"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7394","kev_date_added":null,"published":"2017-04-01"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7396","kev_date_added":null,"published":"2017-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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-06","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can spoof TLS VNC servers by bypassing X.509 certificate verification in the TigerVNC client.","url":"https://insights.sbomify.com/CVE-2011-1775/"}