CVE-2022-1769
High · 7.8CVSS
7.8
EPSS
0.4%
Published
May 17, 2022
CISA due date
—
Cloudanix analysis
A flaw in the Vim text editor can let attackers read parts of computer memory they should not when someone opens a specially made file, which might reveal sensitive information or make the editor crash.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Low
- Impact
- Full Compromise
- Component
- Application
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Buffer over-read allows out-of-bounds memory access when processing specially crafted input in affected Vim versions, enabling potential information disclosure or application crash.
Why it matters to the business
Organizations relying on Vim for editing or scripting face risk of sensitive data leakage from memory or editor instability when users open untrusted files, with limited urgency given low exploit maturity and no observed campaigns.
How an attack unfolds
An attacker crafts a malicious file that triggers the over-read condition upon opening in Vim; the flaw is reached during local file processing without requiring elevated privileges beyond normal user access.
How to fix it
Upgrade Vim to a version containing commit 4748c4bd64610cf943a431d215bb1aad51f8d0b4 or later equivalent release; rebuild from source or use distribution packages that incorporate the fix.
How to confirm the fix worked
Confirm Vim reports version 8.2.4974 or newer; test by attempting to open known trigger files and verify absence of crashes or unexpected behavior; review build logs for the referenced commit.
Typical attack path
- Craft a file that triggers buffer over-read in Vim parser
- Deliver the file to the target user via email, download, or shared storage
- User opens the file with vulnerable Vim version
- Memory contents beyond intended buffer are read, potentially leaking data or causing crash
How to detect it
Review system and application logs for Vim process crashes or abnormal terminations when opening files from untrusted sources; correlate with file access timestamps and user activity around the time of suspected exposure.
What your security team should do
- Prioritize patching developer and administrator workstations that use Vim for source or configuration editing
- Update package repositories and CI/CD images to pull fixed Vim builds
- Scan source control and build systems for pinned vulnerable Vim versions and replace them
The record
Buffer Over-read in GitHub repository vim/vim prior to 8.2.4974.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:11 | vim | 0 | No fix |
| Debian:12 | vim | 0 | 2:9.0.0135-1 |
| Debian:13 | vim | 0 | 2:9.0.0135-1 |
| Mageia:8 | vim | 0 | 8.2.4975-1.mga8 |
| openSUSE:Tumbleweed | vim | 0 | 9.0.0453-2.1 |
Related vulnerabilities
- CVE-2025-9390 A security flaw has been discovered in vim up to 9.1.1615. Also affects vim
- CVE-2025-53905 Vim is an open source, command line text editor. Also affects vim
- CVE-2025-53906 Vim is an open source, command line text editor. Also affects vim
- CVE-2025-29768 Vim, a text editor, is vulnerable to potential data loss with zip.vim and special crafted… Also affects vim
- CVE-2025-27423 Vim is an open source, command line text editor. Also affects vim
- CVE-2025-26603 Vim is a greatly improved version of the good old UNIX editor Vi. Also affects vim
- CVE-2025-1215 A vulnerability classified as problematic was found in vim up to 9.1.1096. Also affects vim
- CVE-2025-24014 Vim is an open source, command line text editor. Also affects vim