Heap-based Buffer Overflow in vim/vim

vim Updated 02 Oct 2025

Summary

22/02/2022
N/A
Yes i
Medium
5.5

CVE-2022-0714: Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4436. Affects vim versions < 8.2.4619-r0. Fixed in 8.2.4619-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

vim is a highly configurable text editor built to enable efficient text editing. It is widely used by developers and system administrators for various programming tasks. The vulnerability in question is a heap-based buffer overflow that affects versions of vim prior to 8.2.4436. This vulnerability can be exploited by an attacker to execute arbitrary code or cause a denial of service.

Vulnerability Detail

The heap-based buffer overflow vulnerability in vim/vim arises from a flaw in the processing of certain input data. By providing specially crafted input, an attacker can trigger the overflow, potentially leading to the execution of arbitrary code or a crash of the application. The vulnerability has a CVSS score of 5.5, indicating a moderate severity level. It is important to note that this vulnerability has been fixed in version 8.2.4436 of vim.

How To Fix

Minimum fixed version

8.2.4619-r0

This is the first release that contains the fix.

sudo apk add --upgrade vim

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a workaround, users can consider restricting the usage of vim to trusted files and avoiding the processing of untrusted input. Additionally, implementing proper input validation and sanitization can help mitigate the risk of exploitation.

Conclusion

The heap-based buffer overflow vulnerability in vim/vim prior to version 8.2.4436 can be exploited by an attacker to execute arbitrary code or cause a denial of service. It is crucial to update vim to the fixed version or apply the provided workaround to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for vim →

Share this vulnerability

FAQ

The vulnerability can allow an attacker to execute arbitrary code or cause a denial of service.

Versions of vim prior to 8.2.4436 are affected by this vulnerability.

Yes, this vulnerability has been fixed in version 8.2.4436 of vim.

To update vim to the fixed version, follow the official update instructions provided by the vim project.

As a workaround, users can restrict the usage of vim to trusted files and implement proper input validation and sanitization.

Related vulnerabilities

Recent vulnerabilities recorded for vim.

How To Fix

Minimum fixed version

8.2.4619-r0

This is the first release that contains the fix.

sudo apk add --upgrade vim

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback