| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in vim. Affected is an unknown function. Performing a manipulation results in use after free. This vulnerability is cataloged as CVE-2022-2817. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in vim (Word Processing Software). This affects an unknown code. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Use After Free in GitHub repository vim/vim prior to 9.0.0212.
The weakness was shared 08/16/2022. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2022-2817 since 08/14/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 9.0.0212 eliminates this vulnerability. Applying the patch 249e1b903a9c0460d618f6dcc59aeb8c03b24b20 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-35055). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 0.52
- 1.0
- 1.22
- 3.0
- 4.0
- 5.0
- 5.1
- 5.2
- 5.3
- 5.4
- 5.5
- 5.6
- 5.7
- 5.8
- 6.0
- 6.1
- 6.2
- 6.3
- 6.3.011
- 6.3.025
- 6.3.030
- 6.3.044
- 6.3.081
- 6.4
- 7.0
- 7.1
- 7.1.38
- 7.1.314
- 7.2
- 7.2a.10
- 8.0
- 8.0.0056
- 8.0.0322
- 8.0.0377
- 8.0.0378
- 8.0.1263
- 8.1.0881
- 8.1.1365
- 8.1.2135
- 8.1.2136
- 8.2
- 8.2.2348
- 8.2.3883
- 8.2.4646
- 8.2.4774
- 8.2.4919
- 8.2.4925
- 8.2.4938
- 8.2.4956
- 8.2.4959
- 9.0
- 9.0.0044
- 9.0.0045
- 9.0.0046
- 9.0.0060
- 9.0.0100
- 9.0.0101
- 9.0.0102
- 9.0.0104
- 9.0.0210
- 9.0.0211
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.3VulDB Meta Temp Score: 7.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: 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 9.0.0212
Patch: 249e1b903a9c0460d618f6dcc59aeb8c03b24b20
Timeline
08/14/2022 🔍08/16/2022 🔍
08/16/2022 🔍
05/27/2026 🔍
Sources
Product: github.comAdvisory: 249e1b903a9c0460d618f6dcc59aeb8c03b24b20
Status: Confirmed
CVE: CVE-2022-2817 (🔍)
GCVE (CVE): GCVE-0-2022-2817
GCVE (VulDB): GCVE-100-206469
EUVD: 🔍
Entry
Created: 08/16/2022 15:26Updated: 05/27/2026 10:24
Changes: 08/16/2022 15:26 (50), 09/11/2022 17:59 (1), 09/11/2022 18:07 (12), 05/27/2026 10:24 (16)
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.