First published: Fri Dec 02 2022(Updated: )
Use After Free in GitHub repository vim/vim prior to 9.0.0789.
Credit: security@huntr.dev security@huntr.dev
Affected Software | Affected Version | How to fix |
---|---|---|
Vim Vim | <9.0.0789 | |
ubuntu/vim | <2:8.0.1453-1ubuntu1.13+ | 2:8.0.1453-1ubuntu1.13+ |
ubuntu/vim | <2:8.1.2269-1ubuntu5.18 | 2:8.1.2269-1ubuntu5.18 |
ubuntu/vim | <2:8.2.3995-1ubuntu2.12 | 2:8.2.3995-1ubuntu2.12 |
ubuntu/vim | <2:7.4.052-1ubuntu3.1+ | 2:7.4.052-1ubuntu3.1+ |
ubuntu/vim | <2:9.0.0813-1 | 2:9.0.0813-1 |
ubuntu/vim | <2:7.4.1689-3ubuntu1.5+ | 2:7.4.1689-3ubuntu1.5+ |
debian/vim | <=2:8.1.0875-5+deb10u2<=2:8.1.0875-5+deb10u6<=2:8.2.2434-3+deb11u1 | 2:9.0.1378-2 2:9.1.0016-1 2:9.1.0377-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-3591 is determined by the impact it has on systems and can range from low to critical.
To fix CVE-2022-3591, update to version 9.0.0789 or higher of the GitHub repository vim/vim.
The affected software for CVE-2022-3591 includes the GitHub repository vim/vim versions prior to 9.0.0789.
No known exploits for CVE-2022-3591 have been reported at this time.
You can find more information about CVE-2022-3591 on the MITRE CVE, Ubuntu Security Notices, and NVD websites.