cve.bz

CVE-2022-3591 Use After Free

7.8 highEPSS 0.4%Fix available

High (7.8). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Use After Free in GitHub repository vim/vim prior to 9.0.0789.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-3591 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-3591?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-3591?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-3591 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 9.0.0789

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14vim2:9.0.0813-1DEBIAN-CVE-2022-3591
Ubuntu20.04:LTSvim2:8.1.2269-1ubuntu5.18UBUNTU-CVE-2022-3591 USN-6420-1
Ubuntu22.04:LTSvim2:8.2.3995-1ubuntu2.12UBUNTU-CVE-2022-3591 USN-6420-1
UbuntuPro:14.04:LTSvim2:7.4.052-1ubuntu3.1+esm13UBUNTU-CVE-2022-3591 USN-6420-1
UbuntuPro:16.04:LTSvim2:7.4.1689-3ubuntu1.5+esm14UBUNTU-CVE-2022-3591 USN-5775-1
UbuntuPro:18.04:LTSvim2:8.0.1453-1ubuntu1.13+esm5UBUNTU-CVE-2022-3591 USN-6420-1
SUSEEnterprise Storage 6, Enterprise Storage 7, Enterprise Storage 7.1 and 22 morevim9.0.1040-150000.5.31.1SUSE-SU-2022:4631-1
SUSELinux Enterprise Server 12 SP2-BCL, Linux Enterprise Server 12 SP4-LTSS, Linux Enterprise Server 12 SP5 and 4 morevim9.0.1234-17.12.1SUSE-SU-2023:0209-1
openSUSELeap 15.3, Leap 15.4, Leap Micro 5.2 and 1 morevim9.0.1040-150000.5.31.1SUSE-SU-2022:4631-1

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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security has rated this issue as having a Low security impact, because the "victim" has to run an untrusted file IN SCRIPT MODE. Someone who is running untrusted files in script mode is equivalent to someone just taking a random python script and running it.

For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle & Updates Policy: https://access.redhat.com/support/policy/updates/errata/.

Red Hat's mitigation

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

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6vimOut of support scope
Red Hat Enterprise Linux 7vimOut of support scope
Red Hat Enterprise Linux 8vimNot affected
Red Hat Enterprise Linux 9vimNot affected

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-3591.

References

Check your stackJSON