{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25268 exists.","fix":"No fix has been published for CVE-2018-25268 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-25268 is a high-severity memory corruption vulnerability in Lizardsystems LanSpy, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-25268 and fix it if it is affected.\n\nWhat it is: CVE-2018-25268 is a high-severity memory corruption vulnerability in Lizardsystems LanSpy, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25268 exists.\n\nAffected product: Lizardsystems LanSpy. 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-2018-25268/ (Markdown: https://insights.sbomify.com/CVE-2018-25268/index.md)","id":"CVE-2018-25268","markdown":"https://insights.sbomify.com/CVE-2018-25268/index.md","name":"CVE-2018-25268","record":{"aliases":["GHSA-m76w-v74r-fqv2"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Network scanning tool","requires_auth":"none","summary":"Attackers can trigger a buffer overflow in LanSpy via oversized scan field input, potentially leading to arbitrary code execution or application crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"lanspy","vendor":"lizardsystems"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"LanSpy 2.0.1.159 contains a local buffer overflow vulnerability that allows attackers to overwrite the instruction pointer by supplying oversized input to the scan field. Attackers can craft a payload with 688 bytes of padding followed by 4 bytes of controlled data to crash the application or potentially achieve code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"LanSpy 2.0.1.159 Local Buffer Overflow via Scan Field","id":"CVE-2018-25268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"ICEWARP 11.0.0.0 Cross-Site Scripting via Email HTML Injection","id":"CVE-2018-25269"},"packages":[],"prev":{"headline":"UltraISO 9.7.1.3519 Buffer Overflow via Output FileName","id":"CVE-2018-25267"},"products":["LanSpy"],"published":"2026-04-22","related":[{"cvss_score":8.6,"headline":"LanSpy 2.0.1.159 Local Buffer Overflow","id":"CVE-2018-25265","kev_date_added":null,"published":"2026-04-22"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["Lizardsystems"]},"summary":"Attackers can trigger a buffer overflow in LanSpy via oversized scan field input, potentially leading to arbitrary code execution or application crashes.","url":"https://insights.sbomify.com/CVE-2018-25268/"}