Skip to content
Fencer Vulns
medium 6.8

CVE-2022-1420 json

Use of Out-of-range Pointer Offset in vim/vim

published 2022-04-21 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24734

cvss
6.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774.

Patch / fix

  • vim vim/vim 8.2.4774
  • vim Debian 14, Debian 13, Debian 12 2:8.2.4793-1

debian advisories DEBIAN-CVE-2022-1420

  • vim Ubuntu 20.04 LTS 2:8.1.2269-1ubuntu5.8
  • vim Ubuntu 22.04 LTS 2:8.2.3995-1ubuntu2.1

ubuntu advisories UBUNTU-CVE-2022-1420

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 RHEL 9 2:8.2.2637-16.el9_0.2
  • vim-X11 RHEL 9 2:8.2.2637-16.el9_0.2
  • vim-common RHEL 9 2:8.2.2637-16.el9_0.2
  • vim-minimal RHEL 9 2:8.2.2637-16.el9_0.2
  • vim-enhanced RHEL 9 2:8.2.2637-16.el9_0.2
  • vim-filesystem RHEL 9 2:8.2.2637-16.el9_0.2

red hat advisories RHSA-2022:5242

  • 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

  • vim-X11 AlmaLinux 9 2:8.2.2637-16.el9_0.2
  • vim-common AlmaLinux 9 2:8.2.2637-16.el9_0.2
  • vim-minimal AlmaLinux 9 2:8.2.2637-16.el9_0.2
  • vim-enhanced AlmaLinux 9 2:8.2.2637-16.el9_0.2
  • vim-filesystem AlmaLinux 9 2:8.2.2637-16.el9_0.2

almalinux advisories ALSA-2022:5242

  • vim CBL-Mariner 2.0 8.2.4925-1

azure linux advisories AZL-9531

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor 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-1420 updated cvss 6.1

vim: Out-of-range Pointer Offset

  • Red Hat Enterprise Linux AppStream (v. 9) vim-X11 8.2.2637-16.el9_0.2, vim-common 8.2.2637-16.el9_0.2, vim-enhanced 8.2.2637-16.el9_0.2 Red Hat Enterprise Linux BaseOS (v. 9) vim 8.2.2637-16.el9_0.2, vim-minimal 8.2.2637-16.el9_0.2, vim-filesystem 8.2.2637-16.el9_0.2
    fixed: vendor fix “Untrusted vim scripts with -s [scriptin] are not recommended to run.” RHSA-2022:5242
  • 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 Virtualization 4 vim-common, vim-enhanced, vim-filesystem
    not 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

1.45% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/a4323ef8-90ea-4e1c-90e9-c778f0ecf326 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 6.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • vim vim/vim

Classification

Weakness
  • CWE-823 Use of Out-of-range Pointer Offset
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns 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.