CVE-2022-1733 json
Heap-based Buffer Overflow in vim/vim
published 4y ago modified 4mo ago also EUVD-2022-25014
- cvss
- 6.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4968.
Patch / fix
- vim vim/vim 8.2.4968
- vim Debian 14, Debian 13, Debian 12 2:9.0.0135-1
debian advisories DEBIAN-CVE-2022-1733
- vim Ubuntu 18.04 LTS 2:8.0.1453-1ubuntu1.12
- vim Ubuntu 20.04 LTS 2:8.1.2269-1ubuntu5.13
- vim Ubuntu 22.04 LTS 2:8.2.3995-1ubuntu2.5
- vim Ubuntu Pro 14.04 LTS 2:7.4.052-1ubuntu3.1+esm8
- vim Ubuntu Pro 16.04 LTS 2:7.4.1689-3ubuntu1.5+esm8
ubuntu advisories UBUNTU-CVE-2022-1733
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 +5 more 9.0.0814-17.9.1
- vim SLES for SAP 15 SP2, SLES for SAP 15 SP1, SLES for SAP 15 +24 more 8.2.5038-150000.5.21.1
suse advisories SUSE-SU-2022:4619-1SUSE-SU-2022:2102-1
- vim openSUSE Tumbleweed 9.0.0453-2.1
opensuse advisories openSUSE-SU-2024:12337-1
- github.com/vim/vim@60ae0e7 commit
Is CVE-2022-1733 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-1733 updated cvss 5.5
vim: Heap-based Buffer Overflow in cindent.c
-
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-filesystem Red Hat Virtualization 4 vim-common, 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
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/6ff03b27-472b-4bef-a2bf-410fae65ff0a referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.6 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- vim vim/vim
Classification
References
-
github.com
/vim/vim/commit/60ae0e71490c97f2871a6344aca61cacf220f813
patch, third-party-advisory
-
huntr.dev
/bounties/6ff03b27-472b-4bef-a2bf-410fae65ff0a
exploit, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/QKIX5HYKWXWG6QBCPPTPQ53GNOFHSAIS/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/IUPOLEX5GXC733HL4EFYMHFU7NISJJZG/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/BFAZTAT5CZC2R6KYDYA2HBAVEDSIX6MW/
vendor-advisory
-
security.gentoo.org
/glsa/202208-32
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/202305-16
vendor-advisory
-
support.apple.com
/kb/HT213488
third-party-advisory
-
seclists.org
/fulldisclosure/2022/Oct/41
mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Oct/28
mailing-list
Sources
- CVE List CVE-2022-1733
- NVD CVE-2022-1733
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.