cve.bz

CVE-2022-0213 Heap-based Buffer Overflow

6.6 mediumExploit referenceEPSS 1.3%Fix available

Medium (6.6). EPSS 1.3% estimated probability of exploitation activity in the next 30 days.

On this page
vim is vulnerable to Heap-based Buffer Overflow

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
EPSS
1.3% (unchanged from 1.3% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 72nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-122 Heap-based Buffer Overflow
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-0213 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-0213?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-0213?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-0213 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vim/vimbefore 8.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian9vim2:8.0.0197-4+deb9u5DLA-2947-1
Debian10vim2:8.1.0875-5+deb10u3DLA-3182-1
Debian12, 13, 14vim2:8.2.4659-1DEBIAN-CVE-2022-0213
Ubuntu18.04:LTSvim2:8.0.1453-1ubuntu1.13UBUNTU-CVE-2022-0213 USN-6026-1
Ubuntu20.04:LTSvim2:8.1.2269-1ubuntu5.14UBUNTU-CVE-2022-0213 USN-6026-1
Ubuntu22.04:LTSvim2:8.2.3995-1ubuntu2.7UBUNTU-CVE-2022-0213 USN-6026-1
UbuntuPro:14.04:LTSvim2:7.4.052-1ubuntu3.1+esm9UBUNTU-CVE-2022-0213 USN-6026-1
UbuntuPro:16.04:LTSvim2:7.4.1689-3ubuntu1.5+esm5UBUNTU-CVE-2022-0213 USN-5458-1
SUSEEnterprise Storage 6, Enterprise Storage 7, Linux Enterprise High Performance Computing 15 SP1-ESPOS and 22 morevim8.2.5038-150000.5.21.1SUSE-SU-2022:2102-1
SUSELinux Enterprise Server 12 SP2-BCL, Linux Enterprise Server 12 SP3-BCL, Linux Enterprise Server 12 SP4-LTSS and 5 morevim9.0.0814-17.9.1SUSE-SU-2022:4619-1
openSUSELeap 15.3, Leap 15.4vim8.2.5038-150000.5.21.1SUSE-SU-2022:2102-1
openSUSETumbleweedvim9.0.0453-2.1openSUSE-SU-2024:12337-1
Alpinev3.12, v3.13, v3.14 and 10 morevim8.2.4173-r0ALPINE-CVE-2022-0213

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Low.

Red Hat's mitigation

Untrusted vim scripts with -s [scriptin] are not recommended to run.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6vimNot affected
Red Hat Enterprise Linux 7vimNot affected
Red Hat Enterprise Linux 8vimNot affected
Red Hat Enterprise Linux 9vimFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Under investigation

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-0213.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON