CVE-2022-1769
HIGHCVSS 7.8/10EPSS 0.37%
Last modified
CVE-2022-1769 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. Buffer Over-read in GitHub repository vim/vim prior to 8.2.4974.. EPSS estimates a 0.37% chance of exploitation in the next 30 days.
Description
Buffer Over-read in GitHub repository vim/vim prior to 8.2.4974.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Vim | Vim | < 8.2.4974 |
| Fedoraproject | Fedora | 34 |
| Fedoraproject | Fedora | 35 |
| Fedoraproject | Fedora | 36 |
| Apple | Macos | < 13.0 |
References
- http://seclists.org/fulldisclosure/2022/Oct/28Mailing List, Third Party Advisory
- http://seclists.org/fulldisclosure/2022/Oct/41Mailing List, Third Party Advisory
- https://github.com/vim/vim/commit/4748c4bd64610cf943a431d215bb1aad51f8d0b4Patch, Third Party Advisory
- https://huntr.dev/bounties/522076b2-96cb-4df6-a504-e6e2f64c171cThird Party Advisory
- https://security.gentoo.org/glsa/202208-32Third Party Advisory
- https://security.gentoo.org/glsa/202305-16Third Party Advisory
- https://support.apple.com/kb/HT213488Third Party Advisory
- http://seclists.org/fulldisclosure/2022/Oct/28Mailing List, Third Party Advisory
- http://seclists.org/fulldisclosure/2022/Oct/41Mailing List, Third Party Advisory
- https://github.com/vim/vim/commit/4748c4bd64610cf943a431d215bb1aad51f8d0b4Patch, Third Party Advisory
- https://huntr.dev/bounties/522076b2-96cb-4df6-a504-e6e2f64c171cThird Party Advisory
- https://security.gentoo.org/glsa/202208-32Third Party Advisory
- https://security.gentoo.org/glsa/202305-16Third Party Advisory
- https://support.apple.com/kb/HT213488Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-1769?
Buffer Over-read in GitHub repository vim/vim prior to 8.2.4974.
How severe is CVE-2022-1769?
CVE-2022-1769 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.37% probability of exploitation in the next 30 days.
How do I fix CVE-2022-1769?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-1763Due to missing checks the Static Page eXtended WordPress plu…5.4
- CVE-2022-1764The WP-chgFontSize WordPress plugin through 1.8 does not hav…5.4
- CVE-2022-1765The Hot Linked Image Cacher WordPress plugin through 1.16 is…8.8
- CVE-2022-1766Anchore Enterprise anchorectl version 0.1.4 improperly store…7.5
- CVE-2022-1767Server-Side Request Forgery (SSRF) in GitHub repository jgra…7.5
- CVE-2022-1768The RSVPMaker plugin for WordPress is vulnerable to unauthen…7.5
- CVE-2022-1770Improper Privilege Management in GitHub repository polonel/t…8.8
- CVE-2022-1771Uncontrolled Recursion in GitHub repository vim/vim prior to…5.5
- CVE-2022-1772The Google Places Reviews WordPress plugin before 2.0.0 does…4.8
- CVE-2022-1773The WP Athletics WordPress plugin through 1.1.7 does not san…6.1
- CVE-2022-1774Exposure of Sensitive Information to an Unauthorized Actor i…6.1
- CVE-2022-1775Weak Password Requirements in GitHub repository polonel/trud…9.8
Are you affected by CVE-2022-1769?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST