{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-22134 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-22134 is a medium-severity memory corruption vulnerability in Netapp Bootstrap Os, published on 13 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-22134 and fix it if it is affected.\n\nWhat it is: CVE-2025-22134 is a medium-severity memory corruption vulnerability in Netapp Bootstrap Os, published on 13 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-22134 in the wild and no public exploit code.\n\nAffected product: Netapp Bootstrap Os. 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-22134/ (Markdown: https://insights.sbomify.com/CVE-2025-22134/index.md)","id":"CVE-2025-22134","markdown":"https://insights.sbomify.com/CVE-2025-22134/index.md","name":"CVE-2025-22134","record":{"aliases":["ALPINE-CVE-2025-22134","AZL-55500","AZL-55582","BELL-CVE-2025-22134","CLSA-2025-1765286037","DEBIAN-CVE-2025-22134","ECHO-392a-f4a0-dbde","GHSA-5rgf-26wj-48v8","MGASA-2025-0014","OESA-2025-1166","UBUNTU-CVE-2025-22134","USN-7220-1"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vim text editor","requires_auth":"low_privilege","summary":"A heap-buffer overflow in Vim allows attackers to cause crashes or potentially execute code when visual mode is active during buffer switching.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"neovim","vendor":"neovim"},{"product":"bootstrap_os","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-122","name":"Heap-based Buffer Overflow"}],"description":"When switching to other buffers using the :all command and visual mode still being active, this may cause a heap-buffer overflow, because Vim does not properly end visual mode and therefore may try to access beyond the end of a line in a buffer. In Patch 9.1.1003 Vim will correctly reset the visual mode before opening other windows and buffers and therefore fix this bug. In addition it does verify that it won't try to access a position if the position is greater than the corresponding buffer line. Impact is medium since the user must have switched on visual mode when executing the :all ex command. The Vim project would like to thank github user gandalf4a for reporting this issue. The issue has been fixed as of Vim patch v9.1.1003","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":"heap-buffer-overflow with visual mode in Vim \u003c 9.1.1003","id":"CVE-2025-22134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"netapp:bootstrap_os","products":["netapp:bootstrap_os","vim:vim"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Tabby has a TCC Bypass via Misconfigured Node Fuses","id":"CVE-2025-22136"},"packages":[],"prev":{"headline":"WeGIA Allows Arbitrary File Upload with Remote Code Execution (RCE)","id":"CVE-2025-22133"},"products":["vim"],"published":"2025-01-13","related":[{"cvss_score":8.6,"headline":"Command injection in n/a","id":"CVE-2019-12735","kev_date_added":null,"published":"2019-06-05"},{"cvss_score":7.8,"headline":"Use After Free in vim/vim","id":"CVE-2022-3591","kev_date_added":null,"published":"2022-12-02"},{"cvss_score":6.6,"headline":"Vim: Heap Buffer Overflow in spell file loading","id":"CVE-2026-45130","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":6.6,"headline":"Heap Overflow in Vim","id":"CVE-2026-25749","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":4.5,"headline":"Vim heap-use-after-free in src/arglist.c:207","id":"CVE-2024-43374","kev_date_added":null,"published":"2024-08-15"},{"cvss_score":4.2,"headline":"Vim \u003c v9.1.0648 has a double-free in dialog_changed()","id":"CVE-2024-41965","kev_date_added":null,"published":"2024-08-01"}],"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":"A heap-buffer overflow in Vim allows attackers to cause crashes or potentially execute code when visual mode is active during buffer switching.","url":"https://insights.sbomify.com/CVE-2025-22134/"}