Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > JMX-RMI vulnerability

JMX-RMI vulnerability

Table of contents

Overview

The following article provides an example of how the Java Management Extensions/Java Remote Method Invocation (JMX/RMI) vulnerability can impact Java-based applications:

Vulnerability and Exploit Database

Environment

  • All WHD versions

Detail

It was discovered that VMware vCenter® binds an unauthenticated JMX/RMI service to the network stack, allowing an attacker to achieve remote code execution and provide SYSTEM-level access to its hosts.

Web Help Desk is safe. The JMX Vulnerability does not apply to Web Help Desk.

If you choose to disable local access to the JMX agent, perform the following steps:

 

For Linux:

  1. Log in to the appliance as an administrator.
  2. Navigate to:
    usr\local\webhelpdesk\conf\
  3. Open the whd.conf file using a text editor (such as Notepad).
  4. Scroll down to the JAVA_OPTS section and add the following parameters:
    JAVA_OPTS="-XX:+DisableAttachMechanism -Dsun.rmi.transport.tcp.maxConnectionThreads=0"
  5. Save and close the file.
  6. Restart Web Help Desk to enable the changes. 

 

For Windows:

  1. Stop Web Help Desk services.
  2. Navigate to C:\Program Files\WebHelpDesk\bin\wrapper\conf\:
  3. Open the wrapper_template.conf file using a text editor (such as Notepad).
  4. Scroll down to the Java Additional Parameters section and add the following parameters (**note**Please make sure that .18 & .19 is the next number in sequence):

    wrapper.java.additional.18=-XX:+DisableAttachMechanism

    wrapper.java.additional.19=-Dsun.rmi.transport.tcp.maxConnectionThreads=0

  5. Save and close the file.
  6. Restart Web Help Desk to enable the changes. 

 

Last modified

Tags

Classifications

Public