Bug 1539157 – CVE-2018-6196 w3m: Infinite recursion in HTMLlineproc0

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

Bug 1539157 - (CVE-2018-6196) CVE-2018-6196 w3m: Infinite recursion in HTMLlineproc0

Summary:	CVE-2018-6196 w3m: Infinite recursion in HTMLlineproc0

Status:	CLOSED NEXTRELEASE

Aliases:	CVE-2018-6196

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

Depends On:	1539158 1539159 1539160
Blocks:
	Show dependency tree / graph

Reported:	2018-01-26 14:34 EST by Pedro Sampaio
Modified:	2018-06-24 04:52 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	w3m 0.5.3+git20180125
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-06-24 04:52:38 EDT
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 Pedro Sampaio 2018-01-26 14:34:54 EST

w3m through 0.5.3 is prone to an infinite recursion flaw in HTMLlineproc0 because the feed_table_block_tag function in table.c does not prevent a negative indent value.

Upstream bug:

https://github.com/tats/w3m/issues/88

Upstream patch:

https://github.com/tats/w3m/commit/8354763b90490d4105695df52674d0fcef823e92

Comment 1 Pedro Sampaio 2018-01-26 14:36:06 EST

Created w3m tracking bugs for this issue:

Affects: epel-7 [bug 1539160]
Affects: fedora-all [bug 1539159]

Comment 3 Parag Nemade 2018-06-24 04:52:38 EDT

Fixed for all the requested releases.

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