{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-43802 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-43802 is a medium-severity memory corruption vulnerability in vim, published on 26 Aug 2024. 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-2024-43802 and fix it if it is affected.\n\nWhat it is: CVE-2024-43802 is a medium-severity memory corruption vulnerability in vim, published on 26 Aug 2024. 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-2024-43802 in the wild and no public exploit code.\n\nAffected product: 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-2024-43802/ (Markdown: https://insights.sbomify.com/CVE-2024-43802/index.md)","id":"CVE-2024-43802","markdown":"https://insights.sbomify.com/CVE-2024-43802/index.md","name":"CVE-2024-43802","record":{"aliases":["ALPINE-CVE-2024-43802","AZL-48221","AZL-48282","BELL-CVE-2024-43802","CLSA-2024-1729193618","DEBIAN-CVE-2024-43802","GHSA-4ghr-c62x-cqfh","OESA-2024-2115","UBUNTU-CVE-2024-43802","USN-7048-1","USN-7048-2"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vim text editor","requires_auth":"none","summary":"A heap-buffer overflow in Vim's typeahead buffer handling can cause a crash when specific error conditions and mappings are active.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the current position in the typeahead buffer but does not check whether there is enough space left in the buffer to handle the next characters.  So this may lead to the tb_off position within the typebuf variable to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g. ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before advancing the off position. If not, fall back to flush current typebuf contents. It's not quite clear yet, what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to flush the typeahead buffer) in comnination with several long mappgins and so it may eventually move the off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to have several mappings active and run into some error condition. But when this happens, this will cause a crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no known workarounds for this issue.","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 in ins_typebuf() in Vim \u003c 9.1.0697","id":"CVE-2024-43802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"BMO can expose particularly named secrets from other namespaces via BMH CRD","id":"CVE-2024-43803"},"packages":[],"prev":{"headline":"Privilege escalation to admin from a low-privileged user via SVG upload in Jellyfin","id":"CVE-2024-43801"},"products":["vim"],"published":"2024-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-03","vendors":["vim"]},"summary":"A heap-buffer overflow in Vim's typeahead buffer handling can cause a crash when specific error conditions and mappings are active.","url":"https://insights.sbomify.com/CVE-2024-43802/"}