Description
In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Apache Software Foundation | Apache JMeter | 2.x, 3.x | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | jakarta-jmeter | No fix yet | — |
| Debian 13 | jakarta-jmeter | No fix yet | — |
| Debian 12 | jakarta-jmeter | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | jakarta-jmeter | No fix yet | — |
| Ubuntu 26.04 LTS | jakarta-jmeter | No fix yet | — |
| Ubuntu 25.10 | jakarta-jmeter | No fix yet | — |
| Ubuntu 24.04 LTS | jakarta-jmeter | No fix yet | — |
| Ubuntu 22.04 LTS | jakarta-jmeter | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | jakarta-jmeter | No fix yet | — |
| Ubuntu 18.04 LTS | jakarta-jmeter | No fix yet | — |
| Ubuntu 16.04 LTS | jakarta-jmeter | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Maven | org.apache.jmeter:ApacheJMeter | < 4.0 | 4.0 | GHSA-j7j7-g4ww-pxg5 |
References
- 103068 vdb-entry
- [www-announce] 20180211 CVE-2018-1287: Apache JMeter binds RMI server to wildcard in distributed mode (based on RMI) mailing-list
- [jmeter-issues] 20190609 [Bug 62039] [CVE-2018-1287 & CVE-2018-1297] Distributed testing : Secure RMI connection by SSL and certificate and bind to host defined "java.rmi.server.hostname" system property mailing-list