CVE-2016-6330: Critical severity red hat jboss operations network vulnerability

Published Aug 22, 2016
·
Updated

The fix for CVE-2016-3737 in JON 3.3.6 was deemed to be incomplete. While we included a documentation fix in the installation guide which explained how to mitigate the issue, we provided misleading information in the security advisory for JON 3.3.6, that it was fixed by that update, which was not correct. To fix this issue, you need to configure SSL authentication for the JON Server/Agent communication. Please see the documentation for details on how to do that: https://access.redhat.com/documentation/en-US/RedHatJBossOperationsNetwork/3.3/html/AdminandConfig/JBossONandSSL-Authentication.html 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 Administration and Configuration guide 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.

Other sources

The server in Red Hat JBoss Operations Network (JON), when SSL authentication is not configured for JON server / agent communication, allows remote attackers to execute arbitrary code via a crafted HTTP request, related to message deserialization. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-3737.

MITRE

Affected Software

16 affected components
redhat JBoss Operations Network=3.0
redhat JBoss Operations Network=3.0.1
redhat JBoss Operations Network=3.1
redhat JBoss Operations Network=3.1.1
redhat JBoss Operations Network=3.1.2
redhat JBoss Operations Network=3.1.4
redhat JBoss Operations Network=3.2.0
redhat JBoss Operations Network=3.2.1
redhat JBoss Operations Network=3.2.2
redhat JBoss Operations Network=3.2.3
redhat JBoss Operations Network=3.3.1
redhat JBoss Operations Network=3.3.2
redhat JBoss Operations Network=3.3.3
redhat JBoss Operations Network=3.3.4
redhat JBoss Operations Network=3.3.5
redhat JBoss Operations Network=3.3.6

Event History

Aug 22, 2016
Data Sourced
via Red Hat·01:01 AM
DescriptionSeverityAffected Software
Sep 27, 2016
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-6330?

CVE-2016-6330 has a medium severity rating due to the incomplete fix for a prior vulnerability.

2

How do I fix CVE-2016-6330?

To mitigate CVE-2016-6330, follow the updated documentation and apply the recommended configurations outlined in the security advisor.

3

What versions of Red Hat JBoss Operations Network are affected by CVE-2016-6330?

CVE-2016-6330 affects Red Hat JBoss Operations Network versions 3.0 through 3.3.6.

4

Is there a patch available for CVE-2016-6330?

Yes, a patch is available as part of the security updates for Red Hat JBoss Operations Network.

5

What are the implications of ignoring CVE-2016-6330?

Ignoring CVE-2016-6330 may leave the system vulnerable to exploitation via an incomplete fix for a previously reported issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203