| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in vim up to 8.1. This affects an unknown function. This manipulation causes use after free. This vulnerability is tracked as CVE-2022-1898. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability has been found in vim up to 8.1 (Word Processing Software) and classified as critical. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 05/27/2022. The advisory is shared at huntr.dev. This vulnerability is known as CVE-2022-1898 since 05/26/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 8.2 eliminates this vulnerability. Applying the patch e2fa213cf571041dbd04ab0329303ffdc980678a 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 vulnerability database at EUVD (EUVD-2022-25170). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
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: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: vim 8.2
Patch: e2fa213cf571041dbd04ab0329303ffdc980678a
Timeline
05/26/2022 🔍05/27/2022 🔍
05/27/2022 🔍
04/12/2026 🔍
Sources
Product: github.comAdvisory: e2fa213cf571041dbd04ab0329303ffdc980678a
Status: Confirmed
CVE: CVE-2022-1898 (🔍)
GCVE (CVE): GCVE-0-2022-1898
GCVE (VulDB): GCVE-100-200857
EUVD: 🔍
Entry
Created: 05/27/2022 12:53Updated: 04/12/2026 08:56
Changes: 05/27/2022 12:53 (50), 06/01/2022 15:05 (2), 04/12/2026 08:56 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.