Heap-based Buffer Overflow Affecting vim-enhanced package, versions *


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-VIMENHANCED-7853712
  • published30 Aug 2024
  • disclosed26 Aug 2024

Introduced: 26 Aug 2024

CVE-2024-43802  (opens in a new tab)
CWE-122  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 vim-enhanced.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vim-enhanced package and not the vim-enhanced package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1