vim up to 8.2.4925 regexp.c vim_regexec_string null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in vim. This issue affects the function vim_regexec_string of the file regexp.c. Performing a manipulation results in null pointer dereference.
This vulnerability is known as CVE-2022-1674. Remote exploitation of the attack is possible. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in vim (Word Processing Software). This affects the function vim_regexec_string of the file regexp.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability.
The weakness was published 05/12/2022. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2022-1674 since 05/11/2022. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 8.2.4938 eliminates this vulnerability. Applying the patch a59f2dfd0cf9ee1a584d3de5b7c2d47648e79060 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-24960). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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
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.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.6
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
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.4938
Patch: a59f2dfd0cf9ee1a584d3de5b7c2d47648e79060
Timeline
05/11/2022 🔍05/12/2022 🔍
05/12/2022 🔍
04/10/2026 🔍
Sources
Product: github.comAdvisory: a59f2dfd0cf9ee1a584d3de5b7c2d47648e79060
Status: Confirmed
CVE: CVE-2022-1674 (🔍)
GCVE (CVE): GCVE-0-2022-1674
GCVE (VulDB): GCVE-100-199665
EUVD: 🔍
Entry
Created: 05/12/2022 15:07Updated: 04/10/2026 10:32
Changes: 05/12/2022 15:07 (51), 05/14/2022 17:40 (2), 04/10/2026 10:32 (16)
Complete: 🔍
Cache ID: 216:D12: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.