Bug 1421613 – CVE-2017-5953 vim: Tree length values not validated properly when handling a spell file

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

Bug 1421613 - (CVE-2017-5953) CVE-2017-5953 vim: Tree length values not validated properly when handling a spell file

Summary:	CVE-2017-5953 vim: Tree length values not validated properly when handling a ...

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-5953

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=20170208,reported=2...
Keywords:	Security

Depends On:	1421652
Blocks:	1421615
	Show dependency tree / graph

Reported:	2017-02-13 04:17 EST by Andrej Nemec
Modified:	2017-03-06 00:50 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-02-23 02:47:46 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-02-13 04:17:18 EST

It was found that vim does not properly validate values for tree length when handling a spell file, which may result in an integer overflow at a memory allocation site and a resultant buffer overflow.

Upstream bug:

https://groups.google.com/forum/#!topic/vim_dev/t-3RSdEnrHY

Upstream patch:

https://github.com/vim/vim/commit/399c297aa93afe2c0a39e2a1b3f972aebba44c9d

Comment 1 Andrej Nemec 2017-02-13 06:09:57 EST

Created vim tracking bugs for this issue:

Affects: fedora-all [bug 1421652]

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