{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2775 is a high-severity memory corruption vulnerability in National Instruments LabVIEW 2016 Evaluation, published on 31 Mar 2017. 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-2017-2775 and fix it if it is affected.\n\nWhat it is: CVE-2017-2775 is a high-severity memory corruption vulnerability in National Instruments LabVIEW 2016 Evaluation, published on 31 Mar 2017. 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-2017-2775 in the wild and no public exploit code.\n\nAffected product: National Instruments LabVIEW 2016 Evaluation. 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-2017-2775/ (Markdown: https://insights.sbomify.com/CVE-2017-2775/index.md)","id":"CVE-2017-2775","markdown":"https://insights.sbomify.com/CVE-2017-2775/index.md","name":"CVE-2017-2775","record":{"aliases":["GHSA-f7q2-f9g4-wwg4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LabVIEW engineering software","requires_auth":"none","summary":"A memory corruption vulnerability in LabVIEW allows remote code execution via a specially crafted VI file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"labview","vendor":"ni"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An exploitable memory corruption vulnerability exists in the LvVariantUnflatten functionality in 64-bit versions of LabVIEW before 2015 SP1 f7 Patch and 2016 before f2 Patch. A specially crafted VI file can cause a user controlled value to be used as a loop terminator resulting in internal heap corruption. An attacker controlled VI file can be used to trigger this vulnerability, exploitation could lead to remote code execution.","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":"Memory corruption in LabVIEW 2016 Evaluation","id":"CVE-2017-2775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-2776"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-2774"},"products":["LabVIEW 2016 Evaluation"],"published":"2017-03-31","related":[{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2013-5022","kev_date_added":null,"published":"2013-08-06"},{"cvss_score":8.5,"headline":"Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-16233","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-16234","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64201","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64202","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64203","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":8.5,"headline":"Out-of-Bounds Write Vulnerability in NI LabVIEW when loading VI","id":"CVE-2026-64204","kev_date_added":null,"published":"2026-08-25"}],"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-05","vendors":["National Instruments"]},"summary":"A memory corruption vulnerability in LabVIEW allows remote code execution via a specially crafted VI file.","url":"https://insights.sbomify.com/CVE-2017-2775/"}