CVE-2018-1287

highpriority · track · 40EPSS 0.034 · 89 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

3.35% (89th) EPSS

CVSS 7.5 · high

Is it mine?

25 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-26

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.

cvss

Technical severity, 0–10. One row per scoring source.

9.8

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.5–9.8

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 6.4

v3.09.8criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USexploitability 3.9 · impact 5.9

v3.09.8criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · OSV

v3.09criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-347US

affected products (25)

Products and version ranges known to be affected.

Apache Software Foundation Apache JMeter≤ 2.xenisa_euvdEU
Apache Software Foundation Apache JMeter≤ 3.xenisa_euvdEU
apache jmeter= 2.1nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.10nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.11nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.12nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.13nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.2nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.3nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.3.1nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.3.2nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.3.3nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.3.4nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.4nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.5nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.5.1nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.6nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.7nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.8nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*
apache jmeter= 2.9nvdUScpe:2.3:a:apache:jmeter:*:*:*:*:*:*:*:*

showing 20 of 25

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-j7j7-g4ww-pxg5Missing certificate validation in Apache JMeter2022-05-13ghsa · osvUS
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.

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2018-02-14modified 2026-06-17

references (11)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan