Use of a Broken or Risky Cryptographic Algorithm Affecting jakarta-jmeter package, versions *


Severity

Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.4% (74th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-JAKARTAJMETER-345775
  • published6 Mar 2019
  • disclosed6 Mar 2019

Introduced: 6 Mar 2019

CVE-2019-0187  (opens in a new tab)
CWE-327  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable jakarta-jmeter.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jakarta-jmeter package and not the jakarta-jmeter package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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 upgrade to JMeter 5.1 is also advised.