high
7.8
CWE
416
Advisory Published
Updated

CVE-2022-1616: Use after free in append_command in vim/vim

First published: Sat May 07 2022(Updated: )

Last updated 24 July 2024

Credit: CVE-2022-0261 CVE-2022-0318 CVE-2022-0319 CVE-2022-0351 CVE-2022-0359 CVE-2022-0361 CVE-2022-0368 CVE-2022-0392 CVE-2022-0554 CVE-2022-0572 CVE-2022-0629 CVE-2022-0685 CVE-2022-0696 CVE-2022-0714 CVE-2022-0729 CVE-2022-0943 CVE-2022-1381 CVE-2022-1420 CVE-2022-1725 CVE-2022-1616 CVE-2022-1619 CVE-2022-1620 CVE-2022-1621 CVE-2022-1629 CVE-2022-1674 CVE-2022-1733 CVE-2022-1735 CVE-2022-1769 CVE-2022-1927 CVE-2022-1942 CVE-2022-1968 CVE-2022-1851 CVE-2022-1897 CVE-2022-1898 CVE-2022-1720 CVE-2022-2000 CVE-2022-2042 CVE-2022-2124 CVE-2022-2125 CVE-2022-2126 security@huntr.dev security@huntr.dev

Affected SoftwareAffected VersionHow to fix
Vim Vim<8.2.4895
Fedoraproject Fedora=34
Fedoraproject Fedora=35
Fedoraproject Fedora=36
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Apple macOS<13.0
<13
13
debian/vim<=2:8.2.2434-3+deb11u1
2:9.0.1378-2
2:9.1.0777-1

Remedy

https://github.com/vim/vim/commit/d88934406c5375d88f8f1b65331c9f0cab68cc6c

Remedy

https://huntr.dev/bounties/40f1d75f-fb2f-4281-b585-a41017f217e2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Peer vulnerabilities

(Found alongside the following vulnerabilities)

Frequently Asked Questions

  • What is CVE-2022-1616?

    CVE-2022-1616 is a vulnerability in Vim that allows for a use-after-free condition in the append_command function, leading to software crashes, bypassing protection mechanisms, memory modification, and potential remote code execution.

  • How does CVE-2022-1616 impact Vim?

    CVE-2022-1616 can cause Vim to crash, bypass protection mechanisms, modify memory, and potentially allow an attacker to execute code remotely.

  • Which versions of Vim are affected by CVE-2022-1616?

    Vim versions prior to 8.2.4895 are affected by CVE-2022-1616.

  • How can I fix CVE-2022-1616?

    To fix CVE-2022-1616, update Vim to version 8.2.4895 or later.

  • Where can I find more information about CVE-2022-1616?

    You can find more information about CVE-2022-1616 at the following references: [reference 1](https://huntr.dev/bounties/40f1d75f-fb2f-4281-b585-a41017f217e2), [reference 2](https://github.com/vim/vim/commit/d88934406c5375d88f8f1b65331c9f0cab68cc6c), [reference 3](https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/A6BY5P7ERZS7KXSBCGFCOXLMLGWUUJIH/)

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203