Bug 1315747 (CVE-2016-2146)

Summary:	CVE-2016-2146 mod_auth_mellon: Failure to limit amount of POST data submitted by client
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	gmollett, security-response-team, ssorce
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-10 06:00:01 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:	1316296
Bug Blocks:	1315749

Description Adam Mariš 2016-03-08 14:07:06 UTC

It was reported that am_read_post_data() failed to limit the amount of POST data submitted by
the client. If the memory allocation for reading the POST data fails, we will get a null pointer dereference when we try to load data into it. If the memory allocation succeeds, we will slowly fill up available memory with post data from the client, causing resource exhaustion.

Upstream bug:

https://github.com/UNINETT/mod_auth_mellon/pull/71

Comment 1 Adam Mariš 2016-03-08 14:07:13 UTC

Acknowledgments:

Name: Olav Morken (Uninett)
Upstream: Vincent Rasneur

Comment 2 Adam Mariš 2016-03-08 14:08:12 UTC

Note that fixing commit is the same as for CVE-2016-2145.

Comment 3 Garth Mollett 2016-03-09 22:10:35 UTC

Public via:
https://sympa.uninett.no/lists/uninett.no/arc/modmellon/2016-03/msg00000.html

Comment 4 Garth Mollett 2016-03-09 22:12:47 UTC

Created mod_auth_mellon tracking bugs for this issue:

Affects: fedora-all [bug 1316296]

Comment 6 Fedora Update System 2016-03-20 02:29:22 UTC

mod_auth_mellon-0.11.1-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.