What is the severity of CVE-2016-9585?

CVE-2016-9585 is classified as a moderate severity vulnerability that could lead to Denial of Service attacks.

How do I fix CVE-2016-9585?

To mitigate CVE-2016-9585, ensure that Remote JMX is not exposed or consider upgrading to a patched version of JBoss EAP.

Which versions of software are affected by CVE-2016-9585?

CVE-2016-9585 affects Red Hat JBoss EAP version 5.0.0.

What kind of attack can exploit CVE-2016-9585?

CVE-2016-9585 can be exploited to perform Denial of Service attacks by sending crafted data to the JMX endpoint.

Can I safely expose Remote JMX on JBoss EAP 5?

Exposing Remote JMX on JBoss EAP 5 is unsafe due to CVE-2016-9585 and should be avoided unless proper security measures are in place.

Vulnerability/
CVE-2016-9585

medium

5.3

CWE

502

14/12/2016

9/3/2018

6/8/2024

CVE-2016-9585

First published: Wed Dec 14 2016(Updated: )

If a user exposes Remote JMX on EAP 5, or SOA-P 5 they could be vulnerable to a Denial of Service Attack.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Red Hat JBoss Enterprise Application Platform	=5.0.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9585?
CVE-2016-9585 is classified as a moderate severity vulnerability that could lead to Denial of Service attacks.
How do I fix CVE-2016-9585?
To mitigate CVE-2016-9585, ensure that Remote JMX is not exposed or consider upgrading to a patched version of JBoss EAP.
Which versions of software are affected by CVE-2016-9585?
CVE-2016-9585 affects Red Hat JBoss EAP version 5.0.0.
What kind of attack can exploit CVE-2016-9585?
CVE-2016-9585 can be exploited to perform Denial of Service attacks by sending crafted data to the JMX endpoint.
Can I safely expose Remote JMX on JBoss EAP 5?
Exposing Remote JMX on JBoss EAP 5 is unsafe due to CVE-2016-9585 and should be avoided unless proper security measures are in place.

agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2016-9585
agent/references
agent/severity
agent/last-modified-date
agent/author
agent/weakness
agent/event
agent/description
agent/trending
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/redhat
canonical/red hat jboss enterprise application platform
version/red hat jboss enterprise application platform/5.0.0

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2016-9585?
CVE-2016-9585 is classified as a moderate severity vulnerability that could lead to Denial of Service attacks.
How do I fix CVE-2016-9585?
To mitigate CVE-2016-9585, ensure that Remote JMX is not exposed or consider upgrading to a patched version of JBoss EAP.
Which versions of software are affected by CVE-2016-9585?
CVE-2016-9585 affects Red Hat JBoss EAP version 5.0.0.
What kind of attack can exploit CVE-2016-9585?
CVE-2016-9585 can be exploited to perform Denial of Service attacks by sending crafted data to the JMX endpoint.
Can I safely expose Remote JMX on JBoss EAP 5?
Exposing Remote JMX on JBoss EAP 5 is unsafe due to CVE-2016-9585 and should be avoided unless proper security measures are in place.