CVE-2018-1287
Missing certificate validation in Apache JMeter
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2018-1287- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2018-1287- Updated
- 2026-11-02
EUVDEUVD-2022-4306 No score
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.
- Record
EUVD-2022-4306- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-j7j7-g4ww-pxg5
Missing certificate validation in Apache JMeter
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. This only affect those running in Distributed mode.
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.
- Record
GHSA-j7j7-g4ww-pxg5- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-347
- Updated
- 2026-11-02
OSV
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.
- Record
CVE-2018-1287- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2018-1287
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.
- Record
DEBIAN-CVE-2018-1287- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-j7j7-g4ww-pxg5
Missing certificate validation in Apache JMeter
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. This only affect those running in Distributed mode.
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.
- Record
GHSA-j7j7-g4ww-pxg5- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-347
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2018-1287
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.
- Record
UBUNTU-CVE-2018-1287- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
org.apache.jmeter:ApacheJMeterMaven |
before 4.0 | 4.0 |
jakarta-jmeterDebian:12 |
All versions, plus listed versions 2.13-52.13-6.12.13-7 |
None known |
jakarta-jmeterDebian:13 |
All versions, plus listed versions 2.13-52.13-6.12.13-7 |
None known |
jakarta-jmeterDebian:14 |
All versions, plus listed versions 2.13-52.13-6.12.13-7 |
None known |
org.apache.jmeter:ApacheJMeterMaven |
before 4.0, plus listed versions 2.102.112.122.132.6 Show 7 moreShow less2.72.82.93.03.13.23.3 |
4.0 |
jakarta-jmeterUbuntu:16.04:LTS |
All versions, plus listed versions 2.11-32.11-42.11-5 |
None known |
jakarta-jmeterUbuntu:18.04:LTS |
All versions, plus listed versions 2.13-3 |
None known |
jakarta-jmeterUbuntu:20.04:LTS |
All versions, plus listed versions 2.13-4 |
None known |
jakarta-jmeterUbuntu:22.04:LTS |
All versions, plus listed versions 2.13-42.13-5 |
None known |
jakarta-jmeterUbuntu:24.04:LTS |
All versions, plus listed versions 2.13-5 |
None known |
jakarta-jmeterUbuntu:25.10 |
All versions, plus listed versions 2.13-5 |
None known |
jakarta-jmeterUbuntu:26.10 |
All versions, plus listed versions 2.13-5build12.13-6.1 |
None known |
jakarta-jmeterUbuntu:26.04:LTS |
All versions, plus listed versions 2.13-52.13-5build1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2018-1287 is a critical vulnerability (CVSS 9.8) in Apache Jmeter, published February 14, 2018. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.35%, the 88th percentile. Fixed in org.apache.jmeter:ApacheJMeter 4.0.
References
securityfocus.com/bid/103068
mail-archives.apache.org/mod_mbox/www-announce/201802.mbox/%3CCAH9fUpYsFx1%2Brwz1A%3Dmc7wAgbDHARyj1VrWNg41y9OySuL1mqw%40mail.gmail.com%3E
lists.apache.org/thread.html/31e0adbeca9d865ff74d0906b2248a41a1457cb54c1afbe5947df58b%40%3Cissues.jmeter.apache.org%3E
nvd.nist.gov/vuln/detail/CVE-2018-1287
github.com/apache/jmeter/issues/4677