Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1333618 - (CVE-2016-3737) CVE-2016-3737 JON: The agent/server communication deserializes data, and does not require authentication
CVE-2016-3737 JON: The agent/server communication deserializes data, and does...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Red Hat Product Security
impact=critical,public=20160506,repor...
: Security
Depends On: 1333619 1333620
Blocks: 1333601
  Show dependency treegraph
 
Reported: 2016-05-05 22:20 EDT by Jason Shepherd
Modified: 2018-10-15 19:58 EDT (History)
5 users (show)

See Also:
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:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1519 normal SHIPPED_LIVE Critical: Red Hat JBoss Operations Network 3.3.6 update 2016-08-25 20:44:36 EDT

  None (edit)
Description Jason Shepherd 2016-05-05 22:20:35 EDT
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 1 Jason Shepherd 2016-05-05 22:24:56 EDT
Acknowledgments:
Name: Jason Shepherd (Red Hat)
Comment 4 Jason Shepherd 2016-06-24 00:55:25 EDT
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 11:31:47 EDT
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 19:55:02 EDT
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-17 20:59:57 EDT
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-17 21:01:21 EDT
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 19:58:45 EDT
Acknowledgments:

Name: Jason Shepherd (Red Hat)

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