CVE-2022-3491 json
Heap-based Buffer Overflow in vim/vim
published 3y ago modified 4mo ago also EUVD-2022-42863
- cvss
- 4.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0742.
Patch / fix
- vim vim/vim 9.0.0742
- vim Debian 14, Debian 13, Debian 12 2:9.0.0813-1
debian advisories DEBIAN-CVE-2022-3491
- vim Ubuntu 22.04 LTS 2:8.2.3995-1ubuntu2.12
ubuntu advisories UBUNTU-CVE-2022-3491
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- vim SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +4 more 9.0.1234-17.12.1
- vim SLES for SAP 15 SP3, SLES for SAP 15 SP2, SLES for SAP 15 SP1 +26 more 9.0.1040-150000.5.31.1
suse advisories SUSE-SU-2023:0209-1SUSE-SU-2022:4631-1
Is CVE-2022-3491 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-3491 updated cvss 7.8
vim: Heap-based Buffer Overflow prior to 9.0.0742
-
Red Hat Enterprise Linux 6 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 7 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 8 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystem Red Hat Enterprise Linux 9 vim, vim-X11, vim-common, vim-minimal, vim-enhanced, vim-filesystemnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/6e6e05c2-2cf7-4aa5-a817-a62007bf92cb referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 4.0 | CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- vim vim/vim
Classification
References
-
github.com
/vim/vim/commit/3558afe9e9e904cabb8475392d859f2d2fc21041
patch, third-party-advisory
-
huntr.dev
/bounties/6e6e05c2-2cf7-4aa5-a817-a62007bf92cb
exploit, patch, third-party-advisory
-
security.gentoo.org
/glsa/202305-16
vendor-advisory
Sources
- CVE List CVE-2022-3491
- NVD CVE-2022-3491
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.