Bug 1333618 (CVE-2016-3737)

Summary:	CVE-2016-3737 JON: The agent/server communication deserializes data, and does not require authentication
Product:	[Other] Security Response	Reporter:	Jason Shepherd <jshepherd>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified	CC:	asantos, jshepherd, miburman, osoukup, spinder, theute
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	It was discovered that sending specially crafted HTTP request to the JON server would allow deserialization of that message without authentication. An attacker could use this flaw to cause remote code execution.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-08 02:51:16 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:	1333619, 1333620
Bug Blocks:	1333601

Description Jason Shepherd 2016-05-06 02:20:35 UTC

JBoss Operations Network server deserializes data, and does not require authentication. A malicious payload could be crafted, and sent to a server which when deserialized causes remote code execution.

Comment 4 Jason Shepherd 2016-06-24 04:55:25 UTC

A workaround for this issue it to enable client authentication between servers and agents:

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html

Comment 9 errata-xmlrpc 2016-07-27 15:31:47 UTC

This issue has been addressed in the following products:

   Red Hat JBoss Operations Network 3.3.6 

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

Comment 10 Jason Shepherd 2016-08-11 23:55:02 UTC

Despite it previously being described as a workaround, the configuration change documented below is the actual solution to this issue.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html

Comment 11 Jason Shepherd 2016-08-18 00:59:57 UTC

Mitigation:

Apply the configuration changes described in the documentation here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html
For more information, refer to https://access.redhat.com/articles/2570101.

Comment 12 Jason Shepherd 2016-08-18 01:01:21 UTC

Statement:

It is not feasible to correct this issue with a code change as client SSL certificates need to be created in order to support client authentication.  The installation documentation notes how to mitigate this through the creation of certificates to support SSL authentication.  This mitigation is the best way to correct this issue and, as a result, we will not be releasing any patches to correct the issue.

Comment 13 Jason Shepherd 2018-10-15 23:58:45 UTC

Acknowledgments:

Name: Jason Shepherd (Red Hat)