{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-24014 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-24014 is a medium-severity vulnerability in Vim Vim, published on 20 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-24014 and fix it if it is affected.\n\nWhat it is: CVE-2025-24014 is a medium-severity vulnerability in Vim Vim, published on 20 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-24014 in the wild and no public exploit code.\n\nAffected product: Vim Vim. 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-2025-24014/ (Markdown: https://insights.sbomify.com/CVE-2025-24014/index.md)","id":"CVE-2025-24014","markdown":"https://insights.sbomify.com/CVE-2025-24014/index.md","name":"CVE-2025-24014","record":{"aliases":["ALPINE-CVE-2025-24014","AZL-55815","AZL-55818","BELL-CVE-2025-24014","CLSA-2025-1762455549","DEBIAN-CVE-2025-24014","ECHO-a83c-9abd-3789","GHSA-j3g9-wg22-v955","MGASA-2025-0038","OESA-2025-1136","UBUNTU-CVE-2025-24014","USN-7261-1","USN-7261-2","USN-7815-1"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Vim text editor","requires_auth":"low_privilege","summary":"An attacker can cause a segmentation fault in Vim's silent Ex mode by feeding binary characters, leading to a denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hci_compute_node_firmware","vendor":"netapp"},{"product":"vim","vendor":"vim"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Vim is an open source, command line text editor. A segmentation fault was found in Vim before 9.1.1043. In silent Ex mode (-s -e), Vim typically doesn't show a screen and just operates silently in batch mode. However, it is still possible to trigger the function that handles the scrolling of a gui version of Vim by feeding some binary characters to Vim. The function that handles the scrolling however may be triggering a redraw, which will access the ScreenLines pointer, even so this variable hasn't been allocated (since there is no screen). This vulnerability is fixed in 9.1.1043.","ecosystems":[],"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":"segmentation fault in win_line() in Vim \u003c 9.1.1043","id":"CVE-2025-24014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vim:vim","products":["vim:vim"],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Deno's AES GCM authentication tags are not verified","id":"CVE-2025-24015"},"packages":[],"prev":{"headline":"CodeIgniter validation of header name and value","id":"CVE-2025-24013"},"products":["vim"],"published":"2025-01-20","related":[],"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":"partial"},"state":"PUBLISHED","updated":"2025-03-14","vendors":["vim"]},"summary":"An attacker can cause a segmentation fault in Vim's silent Ex mode by feeding binary characters, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2025-24014/"}