Skip to content
Fencer Intel
high 8.4

CVE-2022-0417 json

Heap-based Buffer Overflow in vim/vim

published 4y ago modified 4mo ago also EUVD-2022-15559

cvss
8.4
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 74%
public exploits
0
none known

Summary

Heap-based Buffer Overflow GitHub repository vim/vim prior to 8.2.

Patch / fix

  • vim vim/vim 8.2
  • vim Debian 14, Debian 13, Debian 12 2:8.2.4659-1

debian advisories DEBIAN-CVE-2022-0417

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

ubuntu advisories UBUNTU-CVE-2022-0417

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 openSUSE Tumbleweed 8.2.4286-1.1

opensuse advisories openSUSE-SU-2024:11812-1

  • vim Alpine 3.15, Alpine 3.14, Alpine 3.13 +1 more 8.2.4619-r0
  • vim Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 8.2.4350-r0

alpine advisories ALPINE-CVE-2022-0417

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • vim CBL-Mariner 2.0 8.2.4743-1

azure linux advisories AZL-8461

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

  • vim Arch Linux 9.0.1225-1

arch linux advisories AVG-2843

Is CVE-2022-0417 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 Fencer

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-0417 updated cvss 7.8

vim: heap-based-buffer-overflow in ex_retab() of src/indent.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
    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.53% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/fc86bc8d-c866-4ade-8b7f-e49cec306d1a referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • vim vim/vim

Classification

Weakness

References

Sources

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.