{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2019-8277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8277 is a high-severity vulnerability in Kaspersky Lab UltraVNC, published on 9 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-8277 and fix it if it is affected.\n\nWhat it is: CVE-2019-8277 is a high-severity vulnerability in Kaspersky Lab UltraVNC, published on 9 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-8277 in the wild and no public exploit code.\n\nAffected product: Kaspersky Lab UltraVNC. 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-2019-8277/ (Markdown: https://insights.sbomify.com/CVE-2019-8277/index.md)","id":"CVE-2019-8277","markdown":"https://insights.sbomify.com/CVE-2019-8277/index.md","name":"CVE-2019-8277","record":{"aliases":["GHSA-w42q-f4mr-jhc4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC server","requires_auth":"none","summary":"An attacker can read stack memory via network connectivity to disclose information and bypass ASLR in UltraVNC server.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Kaspersky","cpe":[{"product":"sinumerik_access_mymachine\\/p2p","vendor":"siemens"},{"product":"sinumerik_pcu_base_win10_software\\/ipc","vendor":"siemens"},{"product":"sinumerik_pcu_base_win7_software\\/ipc","vendor":"siemens"},{"product":"ultravnc","vendor":"uvnc"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"}],"description":"UltraVNC revision 1211 contains multiple memory leaks (CWE-665) in VNC server code, which allows an attacker to read stack memory and can be abused for information disclosure. Combined with another vulnerability, it can be used to leak stack memory and bypass ASLR. This attack appears to be exploitable via network connectivity. These vulnerabilities have been fixed in revision 1212.","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":"Information disclosure in UltraVNC","id":"CVE-2019-8277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in Invision Power Board","id":"CVE-2019-8278"},"packages":[],"prev":{"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8276"},"products":["UltraVNC"],"published":"2019-03-09","related":[{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8268","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8271","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Integer overflow in UltraVNC","id":"CVE-2019-8272","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8273","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8274","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Null dereference in UltraVNC","id":"CVE-2019-8275","kev_date_added":null,"published":"2019-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in UltraVNC","id":"CVE-2019-8258","kev_date_added":null,"published":"2019-03-05"}],"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-08-04","vendors":["Kaspersky Lab"]},"summary":"An attacker can read stack memory via network connectivity to disclose information and bypass ASLR in UltraVNC server.","url":"https://insights.sbomify.com/CVE-2019-8277/"}