{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-27830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-27830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-27830 is a critical vulnerability in n/a, published on 12 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-27830 and fix it if it is affected.\n\nWhat it is: CVE-2023-27830 is a critical vulnerability in n/a, published on 12 Apr 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-27830 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-2023-27830/ (Markdown: https://insights.sbomify.com/CVE-2023-27830/index.md)","id":"CVE-2023-27830","markdown":"https://insights.sbomify.com/CVE-2023-27830/index.md","name":"CVE-2023-27830","record":{"aliases":["GHSA-w347-2542-wgjq"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"TightVNC remote desktop","requires_auth":"low_privilege","summary":"Attackers can escalate privileges on the host OS by replacing legitimate files during file transfers due to TightVNC running with high privileges.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tightvnc","vendor":"tightvnc"}],"cvss":{"score":9,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"TightVNC before v2.8.75 allows attackers to escalate privileges on the host operating system via replacing legitimate files with crafted files when executing a file transfer. This is due to the fact that TightVNC runs in the backend as a high-privileges account.","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":"Privilege escalation in n/a","id":"CVE-2023-27830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2023-27836"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-27826"},"products":["n/a"],"published":"2023-04-12","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2009-0388","kev_date_added":null,"published":"2009-02-04"},{"cvss_score":9.8,"headline":"Buffer Overflow in tvnviewer.exe via Crafted Packet in TightVNC Viewer 2.8.59","id":"CVE-2021-42785","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":9.8,"headline":"Memory corruption in TightVNC","id":"CVE-2019-15678","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":9.8,"headline":"Memory corruption in TightVNC","id":"CVE-2019-15679","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":9.8,"headline":"Memory corruption in TightVNC","id":"CVE-2019-8287","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":7.5,"headline":"Null dereference in TightVNC","id":"CVE-2019-15680","kev_date_added":null,"published":"2019-10-29"}],"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":"total"},"state":"PUBLISHED","updated":"2025-02-08","vendors":["n/a"]},"summary":"Attackers can escalate privileges on the host OS by replacing legitimate files during file transfers due to TightVNC running with high privileges.","url":"https://insights.sbomify.com/CVE-2023-27830/"}