Skip to content
Fencer Intel
high 7.8

CVE-2022-2288 json

Out-of-bounds Write in vim/vim

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

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

Summary

Out-of-bounds Write in GitHub repository vim/vim prior to 9.0.

Patch / fix

  • vim vim/vim 9.0
  • vim Debian 14, Debian 13, Debian 12 2:9.0.0135-1

debian advisories DEBIAN-CVE-2022-2288

  • vim openSUSE Tumbleweed 9.0.0453-2.1

opensuse advisories openSUSE-SU-2024:12337-1

  • vim Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 9.0.0050-r0

alpine advisories ALPINE-CVE-2022-2288

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 9.0.0050-2

azure linux advisories AZL-10060

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

Is CVE-2022-2288 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-2288 updated cvss 5.3

vim: out of bounds write in parse_command_modifiers() at ex_docmd.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
    affected: workaround, no fix planned “Untrusted vim scripts with -s [scriptin] are not recommended to run.”
  • 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.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/a71bdcb7-4e9b-4650-ab6a-fe8e3e9852ad referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.