ESB-2019.0654 - [Win][UNIX/Linux] Apache JMeter: Execute arbitrary code/commands - Remote/unauthenticated 2019-03-04

Printable version
PGP/GPG verifiable version

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2019.0654
         Apache JMeter Missing client auth for RMI connection when
                         distributed test is used
                               4 March 2019

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           Apache JMeter
Publisher:         The Apache Software Foundation
Operating System:  Windows
                   UNIX variants (UNIX, Linux, OSX)
Impact/Access:     Execute Arbitrary Code/Commands -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2019-0187  

Original Bulletin: 
   http://mail-archives.apache.org/mod_mbox/jmeter-user/201903.mbox/%3CCAH9fUpaUQaFbgY1Zh4OvKSL4wdvGAmVt%2Bn4fegibDoAxK5XARw%40mail.gmail.com%3E

- --------------------------BEGIN INCLUDED TEXT--------------------

CVE-2019-0187
Severity: Important
Vendor: The Apache Software Foundation
Affected Versions : JMeter 4.0, 5.0

Description [0]:

Unauthenticated RCE is possible when JMeter is used in distributed mode (-r
or -R command line options).
Attacker can establish a RMI connection to a jmeter-server using
RemoteJMeterEngine and proceed with an attack using untrusted data
deserialization.
This only affect tests running in Distributed mode.
Note that versions before 4.0 are not able to encrypt traffic between the
nodes, nor authenticate the participating nodes so even for those versions,
upgrade to JMeter 5.1 is
also advised.

Mitigation:
  * Users must use last minor version of Java 8 to Java 11
  * Users must upgrade to last JMeter 5.1 version and use the default /
enabled authenticated SSL RMI connection.

Besides, we remind users that in distributed mode, JMeter makes an
Architectural assumption
that it is operating on a 'safe' network. i.e. everyone with access to the
network is considered trusted.

This typically means a dedicated VPN or similar is being used.

Example:
  * Start JMeter server using either jmeter-server or jmeter -s
  * Using another keystore file, if you're able to connect to first server
instance and you don't get "SSLHandshakeException: Received fatal alert:
bad_certificate", you are vulnerable

Credit:
This issue was reported responsibly to the Apache Security Team by Brenden
Meeder.

- - The Apache JMeter Team

[0] https://bz.apache.org/bugzilla/show_bug.cgi?id=62743

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBXHx8CmaOgq3Tt24GAQi9DA/+LXQTM5frL1nyJOn+KbMDJgpplkjsrGH2
FLp4XFCy+KQEZ++VXZjt4W69zAY0oDE+h+T3iMn4QIRmHUhAArSZnH/KOl7l7WHl
gI1rtYFvsc7sLdoJbPDgtjNSmzAmWrkENUcepfcN22+7Pi+hpqaMhuKCeBEzPUAN
4tS71LSpbq8JM61ckuXV2AIlpYeZYwk4e0PYikZK1yWsUZVaNp4bR/UMBNtohsvw
ibaXes0NqXZsjTg5mpLpnMEJpZlNykCS6mozyucV3cLtA4pY0p2rYGmd9FBBgmkT
rQWH7WNilVVaz4tJBYedSYTf7HOMVniNRB2MySpfURf78qF8RB4Mzw+oJlIUg+3G
hIHJgS9eU9lnJTjPpTcpBiUQQwchkPKL5XoZd6cLE2vtqfj9E+m/tyMcXOHiVsz7
gTZx76bMAP13LtH0HgRLXmiY9/fYrA6kh34LM5uRXUcYKjuQ50tSdae7p38a3dLp
hQ+aui34fuVbuBVn3k9x2gCq/uDDBm++R5ht8TyFCMBd7S+v5QiQyZuDrFxI3N5O
eJhr/HIp4OmqOXhc8LMq7wdEdE2JucFzAx9tzyMHb09b8yD1htcqrbUt3r7cHYM/
32Q9nJNkRP2hH3DLFTD2UtlwDZxRoCyiWYLDNBQT97gAUOxzLVmON7/+th/01o+6
0C4XuZpdDUQ=
=blSQ
-----END PGP SIGNATURE-----

« Back to bulletins