Bug 1427945 – CVE-2017-6350 vim: Integer overflow at an unserialize_uep memory allocation site

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1427945 - (CVE-2017-6350) CVE-2017-6350 vim: Integer overflow at an unserialize_uep memory allocation site

Summary:	CVE-2017-6350 vim: Integer overflow at an unserialize_uep memory allocation site

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-6350

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20170213,reported=2...
Keywords:	Security

Depends On:
Blocks:	1427946
	Show dependency tree / graph

Reported:	2017-03-01 09:57 EST by Andrej Nemec
Modified:	2017-03-06 11:04 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	vim 8.0.0378
Doc Type:	If docs needed, set a value
Doc Text:	An integer overflow flaw was found in the way vim handled tree length values when reading an undo file. This bug could result in vim crashing when trying to process corrupted undo files.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-03-06 01:26:37 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2017-03-01 09:57:31 EST

An integer overflow at an unserialize_uep memory allocation site would occur for vim, as it does not properly validate values for tree length when reading a corrupted undo file, which may lead to resultant buffer overflows. 

Upstream bug:

https://groups.google.com/forum/#!topic/vim_dev/QPZc0CY9j3Y

Upstream patch:

https://github.com/vim/vim/commit/0c8485f0e4931463c0f7986e1ea84a7d79f10c75

Note You need to log in before you can comment on or make changes to this bug.