Bug 2004728 (CVE-2021-3796)

Summary: CVE-2021-3796 vim: use-after-free in nv_replace() in normal.c
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bdettelb, caswilli, fjansen, gchamoul, gghezzo, gparvin, jnakfour, jramanat, jwong, karsten, kaycoth, kyoneyam, pahickey, psegedy, saroy, security-response-team, stcannon, vkumar, vmugicag, yozone, zdohnal
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: vim 8.2.3428 Doc Type: If docs needed, set a value
Doc Text:
A use-after-free vulnerability in vim could allow an attacker to input a specially crafted file leading to memory corruption and a potentially exploitable crash or code execution. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-08 10:04:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: Red Hat2006820, 2004729, Red Hat2004973, Red Hat2004974, Red Hat2004975, Red Hat2004976, Red Hat2006821, Red Hat2006823, Red Hat2006824    
Bug Blocks: Embargoed2004623    

Description Guilherme de Almeida Suckevicz 2021-09-15 19:55:48 UTC
vim is vulnerable to Use After Free


Upstream patch:

Comment 1 Guilherme de Almeida Suckevicz 2021-09-15 19:56:05 UTC
Created vim tracking bugs for this issue:

Affects: fedora-all [bug 2004729]

Comment 9 errata-xmlrpc 2021-11-09 19:04:21 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:4517 https://access.redhat.com/errata/RHSA-2021:4517

Comment 10 Product Security DevOps Team 2021-12-08 10:04:19 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):