CVE-2018-1297

When using Distributed Test only (RMI based), Apache JMeter 2.x and 3.x uses an unsecured RMI connection. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.

Published: 2018-02-13 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1297 is rated High Risk (67.5/100): CVSS Critical severity, with high exploitation likelihood (EPSS 10.10%, 95th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1297

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 17.99% 10.10% -7.90%
2 2026-02-14 23.19% 17.99% -5.19%
3 2025-08-30 — 23.19% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1297

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2018-1297

GitHub Security Advisory for CVE-2018-1297

GHSA-7v85-6hv2-rwgw · Severity: critical · Ecosystem: maven — Missing certificate validation in Apache JMeter

OS Trackers for CVE-2018-1297

vendor priority summary link
debian low CVE-2018-1297 low priority: Debian including 1 source packages (jakarta-jmeter), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2018-1297
ubuntu medium CVE-2018-1297 medium priority: Ubuntu including 1 source packages (jakarta-jmeter), 20 status rows across 20 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 12, needs-triage 7, DNE 1. https://ubuntu.com/security/CVE-2018-1297

Affected software / configurations for CVE-2018-1297

Vendor Product Version Raw CPE
apache jmeter 2.1 cpe:2.3:a:apache:jmeter:2.1:*:*:*:*:*:*:*
apache jmeter 2.2 cpe:2.3:a:apache:jmeter:2.2:*:*:*:*:*:*:*
apache jmeter 2.3 cpe:2.3:a:apache:jmeter:2.3:*:*:*:*:*:*:*
apache jmeter 2.3.1 cpe:2.3:a:apache:jmeter:2.3.1:*:*:*:*:*:*:*
apache jmeter 2.3.2 cpe:2.3:a:apache:jmeter:2.3.2:*:*:*:*:*:*:*
apache jmeter 2.3.3 cpe:2.3:a:apache:jmeter:2.3.3:*:*:*:*:*:*:*
apache jmeter 2.3.3 cpe:2.3:a:apache:jmeter:2.3.3:rc1:*:*:*:*:*:*
apache jmeter 2.3.3 cpe:2.3:a:apache:jmeter:2.3.3:rc2:*:*:*:*:*:*
apache jmeter 2.3.4 cpe:2.3:a:apache:jmeter:2.3.4:*:*:*:*:*:*:*
apache jmeter 2.3.4 cpe:2.3:a:apache:jmeter:2.3.4:rc1:*:*:*:*:*:*
apache jmeter 2.3.4 cpe:2.3:a:apache:jmeter:2.3.4:rc2:*:*:*:*:*:*
apache jmeter 2.3.4 cpe:2.3:a:apache:jmeter:2.3.4:rc3:*:*:*:*:*:*
apache jmeter 2.4 cpe:2.3:a:apache:jmeter:2.4:*:*:*:*:*:*:*
apache jmeter 2.5 cpe:2.3:a:apache:jmeter:2.5:*:*:*:*:*:*:*
apache jmeter 2.5 cpe:2.3:a:apache:jmeter:2.5:rc1:*:*:*:*:*:*
apache jmeter 2.5 cpe:2.3:a:apache:jmeter:2.5:rc2:*:*:*:*:*:*
apache jmeter 2.5 cpe:2.3:a:apache:jmeter:2.5:rc3:*:*:*:*:*:*
apache jmeter 2.5.1 cpe:2.3:a:apache:jmeter:2.5.1:*:*:*:*:*:*:*
apache jmeter 2.5.1 cpe:2.3:a:apache:jmeter:2.5.1:rc1:*:*:*:*:*:*
apache jmeter 2.5.1 cpe:2.3:a:apache:jmeter:2.5.1:rc2:*:*:*:*:*:*
apache jmeter 2.5.1 cpe:2.3:a:apache:jmeter:2.5.1:rc3:*:*:*:*:*:*
apache jmeter 2.6 cpe:2.3:a:apache:jmeter:2.6:*:*:*:*:*:*:*
apache jmeter 2.6 cpe:2.3:a:apache:jmeter:2.6:rc1:*:*:*:*:*:*
apache jmeter 2.6 cpe:2.3:a:apache:jmeter:2.6:rc2:*:*:*:*:*:*
apache jmeter 2.7 cpe:2.3:a:apache:jmeter:2.7:*:*:*:*:*:*:*
apache jmeter 2.7 cpe:2.3:a:apache:jmeter:2.7:rc1:*:*:*:*:*:*
apache jmeter 2.7 cpe:2.3:a:apache:jmeter:2.7:rc2:*:*:*:*:*:*
apache jmeter 2.7 cpe:2.3:a:apache:jmeter:2.7:rc3:*:*:*:*:*:*
apache jmeter 2.8 cpe:2.3:a:apache:jmeter:2.8:*:*:*:*:*:*:*
apache jmeter 2.8 cpe:2.3:a:apache:jmeter:2.8:rc1:*:*:*:*:*:*
apache jmeter 2.8 cpe:2.3:a:apache:jmeter:2.8:rc2:*:*:*:*:*:*
apache jmeter 2.9 cpe:2.3:a:apache:jmeter:2.9:*:*:*:*:*:*:*
apache jmeter 2.9 cpe:2.3:a:apache:jmeter:2.9:rc1:*:*:*:*:*:*
apache jmeter 2.9 cpe:2.3:a:apache:jmeter:2.9:rc2:*:*:*:*:*:*
apache jmeter 2.9 cpe:2.3:a:apache:jmeter:2.9:rc3:*:*:*:*:*:*
apache jmeter 2.10 cpe:2.3:a:apache:jmeter:2.10:rc1:*:*:*:*:*:*
apache jmeter 2.10 cpe:2.3:a:apache:jmeter:2.10:rc2:*:*:*:*:*:*
apache jmeter 2.11 cpe:2.3:a:apache:jmeter:2.11:*:*:*:*:*:*:*
apache jmeter 2.11 cpe:2.3:a:apache:jmeter:2.11:rc1:*:*:*:*:*:*
apache jmeter 2.11 cpe:2.3:a:apache:jmeter:2.11:rc2:*:*:*:*:*:*
apache jmeter 2.12 cpe:2.3:a:apache:jmeter:2.12:*:*:*:*:*:*:*
apache jmeter 2.12 cpe:2.3:a:apache:jmeter:2.12:rc1:*:*:*:*:*:*
apache jmeter 2.12 cpe:2.3:a:apache:jmeter:2.12:rc2:*:*:*:*:*:*
apache jmeter 2.13 cpe:2.3:a:apache:jmeter:2.13:*:*:*:*:*:*:*
apache jmeter 2.13 cpe:2.3:a:apache:jmeter:2.13:rc1:*:*:*:*:*:*
apache jmeter 2.13 cpe:2.3:a:apache:jmeter:2.13:rc2:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:*:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:rc1:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:rc2:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:rc3:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:rc4:*:*:*:*:*:*
apache jmeter 3.0 cpe:2.3:a:apache:jmeter:3.0:rc5:*:*:*:*:*:*
apache jmeter 3.1 cpe:2.3:a:apache:jmeter:3.1:*:*:*:*:*:*:*
apache jmeter 3.1 cpe:2.3:a:apache:jmeter:3.1:rc1:*:*:*:*:*:*
apache jmeter 3.1 cpe:2.3:a:apache:jmeter:3.1:rc2:*:*:*:*:*:*
apache jmeter 3.1 cpe:2.3:a:apache:jmeter:3.1:rc3:*:*:*:*:*:*
apache jmeter 3.1 cpe:2.3:a:apache:jmeter:3.1:rc4:*:*:*:*:*:*
apache jmeter 3.2 cpe:2.3:a:apache:jmeter:3.2:*:*:*:*:*:*:*
apache jmeter 3.2 cpe:2.3:a:apache:jmeter:3.2:rc1:*:*:*:*:*:*
apache jmeter 3.2 cpe:2.3:a:apache:jmeter:3.2:rc2:*:*:*:*:*:*
apache jmeter 3.2 cpe:2.3:a:apache:jmeter:3.2:rc3:*:*:*:*:*:*
apache jmeter 3.3 cpe:2.3:a:apache:jmeter:3.3:*:*:*:*:*:*:*
apache jmeter 3.3 cpe:2.3:a:apache:jmeter:3.3:rc1:*:*:*:*:*:*

References for CVE-2018-1297

cvelogic Threat Intelligence