Bug 1341583 (CVE-2016-4459)

Summary:	CVE-2016-4459 mod_cluster: Buffer overflow in mod_manager when sending request with long JVMRoute
Product:	[Other] Security Response	Reporter:	Timothy Walsh <twalsh>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bbaranow, bmaxwell, bperkins, cdewolf, chazlett, csutherl, dandread, darran.lofthouse, dereed, dknox, dosoudil, jawilson, jclere, lgao, mbabacek, myarboro, pgier, psakar, pslavice, rnetuka, rsvoboda, security-response-team, twalsh, vtunka, weli
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	It was discovered that specifying configuration with a JVMRoute path longer than 80 characters will cause segmentation fault leading to a server crash.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-08 02:53:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1341601, 1341602
Bug Blocks:	1341562, 1395463

Description Timothy Walsh 2016-06-01 10:18:03 UTC

Configuration of mod_cluster via JVMRoute longer than 80 characters will cause segfault.

A segmentation fault can occur in Apache HTTPD 2.2. 

The crash is due to a strcpy buffer overflow in mod_cluster's mod_manager.

https://github.com/modcluster/mod_cluster/blob/1.2.9.Final/native/mod_manager/node.c#L227 [Open URL]

If clients send a request with a JVMRoute longer than 80 characters
(the size of the strcpy destination), the strcpy segfaults.

Comment 6 Timothy Walsh 2016-06-02 03:49:36 UTC


Acknowledgments:

Name: Robert Bost (Red Hat)

Comment 10 errata-xmlrpc 2016-10-12 17:02:35 UTC

This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4.10

Via RHSA-2016:2056 https://rhn.redhat.com/errata/RHSA-2016-2056.html

Comment 11 errata-xmlrpc 2016-10-12 17:09:41 UTC

This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7

Via RHSA-2016:2054 https://rhn.redhat.com/errata/RHSA-2016-2054.html

Comment 12 errata-xmlrpc 2016-10-12 17:20:27 UTC

This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6

Via RHSA-2016:2055 https://rhn.redhat.com/errata/RHSA-2016-2055.html

Comment 13 errata-xmlrpc 2016-12-15 22:20:24 UTC

This issue has been addressed in the following products:



Via RHSA-2016:2957 https://rhn.redhat.com/errata/RHSA-2016-2957.html

Comment 14 errata-xmlrpc 2017-01-25 20:05:50 UTC

This issue has been addressed in the following products:

  JBoss Core Services on RHEL 7

Via RHSA-2017:0194 https://access.redhat.com/errata/RHSA-2017:0194

Comment 15 errata-xmlrpc 2017-01-25 20:07:17 UTC

This issue has been addressed in the following products:

  JBoss Core Services on RHEL 6

Via RHSA-2017:0193 https://access.redhat.com/errata/RHSA-2017:0193