Bug 2077734 (CVE-2022-1420) - CVE-2022-1420 vim: Out-of-range Pointer Offset
Summary: CVE-2022-1420 vim: Out-of-range Pointer Offset
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-1420
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2077781 2077786 2077787
Blocks: 2077735
TreeView+ depends on / blocked
 
Reported: 2022-04-22 04:36 UTC by TEJ RATHI
Modified: 2022-07-01 09:42 UTC (History)
7 users (show)

Fixed In Version: vim 8.2.4774
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in Vim. The issue occurs when using a number in a string for the lambda name, triggering an out-of-range pointer offset vulnerability. This flaw allows an attacker to trick a user into opening a crafted script containing an argument as a number and then using it as a string pointer to access any memory location, causing an application to crash and possibly access some memory.
Clone Of:
Environment:
Last Closed: 2022-07-01 09:42:38 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5242 0 None None None 2022-06-28 14:58:27 UTC

Description TEJ RATHI 2022-04-22 04:36:55 UTC 
Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4774.

https://github.com/vim/vim/commit/8b91e71441069b1dde9ac9ff9d9a829b1b4aecca
https://huntr.dev/bounties/a4323ef8-90ea-4e1c-90e9-c778f0ecf326
Comment 1 TEJ RATHI 2022-04-22 09:00:37 UTC 
Created vim tracking bugs for this issue:

Affects: fedora-all [bug 2077781]
Comment 4 errata-xmlrpc 2022-06-28 14:58:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2022:5242 https://access.redhat.com/errata/RHSA-2022:5242
Comment 5 Product Security DevOps Team 2022-07-01 09:42:35 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-1420
Note You need to log in before you can comment on or make changes to this bug.