| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in vim up to 8.1 and classified as critical. The impacted element is an unknown function. Performing a manipulation results in heap-based overflow. This vulnerability is known as CVE-2022-0261. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in vim up to 8.1 (Word Processing Software). It has been classified as critical. This affects an unknown part. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 01/19/2022. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2022-0261 since 01/17/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 212462 (Amazon Linux 2022 : vim-common, vim-data, vim-default-editor (ALAS2022-2022-020)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 8.2 eliminates this vulnerability. Applying the patch 9f8c304c8a390ade133bac29963dc8e56ab14cbc is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (212462) and EUVD (EUVD-2022-15446). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://github.com/vim/vim/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 1.9
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 212462
Nessus Name: Amazon Linux 2022 : vim-common, vim-data, vim-default-editor (ALAS2022-2022-020)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: vim 8.2
Patch: 9f8c304c8a390ade133bac29963dc8e56ab14cbc
Timeline
01/17/2022 🔍01/19/2022 🔍
01/19/2022 🔍
03/25/2026 🔍
Sources
Product: github.comAdvisory: 9f8c304c8a390ade133bac29963dc8e56ab14cbc
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-0261 (🔍)
GCVE (CVE): GCVE-0-2022-0261
GCVE (VulDB): GCVE-100-190725
EUVD: 🔍
Entry
Created: 01/19/2022 14:17Updated: 03/25/2026 05:15
Changes: 01/19/2022 14:17 (50), 01/20/2022 16:31 (3), 12/12/2024 03:38 (16), 05/02/2025 02:00 (3), 11/04/2025 10:50 (17), 11/04/2025 10:51 (14), 03/25/2026 05:15 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.