[IGNITE-13478] Security issue in JMX configuration using ignite.sh

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.10
• Component/s: control.sh
• Release Note: Removed default insecure JMX configuration from scripts. Now JMX can be enabled through JVM_OPTS variable.
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Semyon Danilov
• Reporter: Semyon Danilov
• Created: 23/Sep/20 10:52
• Updated: 22/Oct/20 07:06
• Resolved: 22/Oct/20 07:05

Description

At the moment we have the following code:

functions.sh

 

JMX_PORT=`"$JAVA" -cp "${IGNITE_LIBS}" org.apache.ignite.internal.util.portscanner.GridJmxPortFinder`

#
# This variable defines necessary parameters for JMX
# monitoring and management.
#
# This enables remote unsecure access to JConsole or VisualVM.
#
# ADD YOUR ADDITIONAL PARAMETERS/OPTIONS HERE
#
if [ -n "$JMX_PORT" ]; then
    JMX_MON="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=${JMX_PORT} \
        -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
else
    # If JMX port wasn't found do not initialize JMX.
    echo "$0, WARN: Failed to resolve JMX host (JMX will be disabled): $HOSTNAME"
    JMX_MON=""
fi

So the properties -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false will be set always and there is no way to change them.

 

I propose removal of JMX configuration (in scripts) altogether as it's very insecure and users must configure JMX themselves

 

Issue Links

• causes: IGNITE-13606 Documentation update on JMX default configuration removal
• links to: GitHub Pull Request #8281
• links to: GitHub Pull Request #8304