dbcve.org
JmeterApplication · Apache

CVE-2018-1297

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache JMeter 2.x and 3.x uses unsecured RMI (Remote Method Invocation) connections for distributed testing between master and slave nodes. An attacker with network access to the RMI ports can inject arbitrary code by sending malicious objects to the JMeterEngine, achieving remote code execution.

MitigationUpgrade to JMeter 4.0 or later which includes secured RMI connections, or implement strict network-level access controls (firewalls/VPNs) to restrict access to RMI ports if upgrade is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JmeterApplication
Affected:= 2.1= 2.2= 2.3= 2.3.1= 2.3.2= 2.3.3= 2.3.4= 2.4= 2.5= 2.5.1= 2.6= 2.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JMeter version
    Run 'jmeter --version' or check the JMeter bin directory for the version file. On Windows, run jmeter.bat --version. On Linux/Mac, run jmeter --version or ./jmeter.sh --version.
    Affected if The version output shows any 2.x or 3.x release (e.g., 2.13, 3.0, 3.2, etc.). Note: The specific versions listed (2.1 through 2.7) are explicitly affected, but the advisory states 2.x and 3.x are vulnerable.
  2. Determine if RMI is enabled for distributed testing
    Check the JMeter properties file (jmeter.properties or user.properties) for RMI-related settings. Look for properties like 'server.rmi.localport', 'server.rmi.port', or configurations referencing 'java.rmi'. Also check for any 'remote_hosts' or 'client.rmi' settings.
    Affected if RMI-related properties are uncommented or configured, indicating distributed testing mode is enabled.
  3. Identify exposed RMI ports
    Review jmeter.properties for 'server.rmi.port' (default 4000) and 'server.rmi.localport' settings. Check if these ports are open on the system using 'netstat -an | grep -E "(4000|4099)"' or similar port scanning from another host.
    Affected if RMI ports (default 4000 for server, 1099 for JMX) are listening on network interfaces accessible from untrusted networks.
  4. Verify network accessibility of RMI endpoints
    From an external host or untrusted network segment, attempt to reach the RMI ports (e.g., nmap -p 4000,1099 <jmeter-host>). Check firewall rules or cloud security groups for inbound rules exposing these ports.
    Affected if RMI ports are reachable from network segments outside the trusted administration domain.

You are affected if you run any JMeter 2.x or 3.x version with distributed testing (RMI) enabled and those RMI ports are accessible from networks you do not fully control.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to JMeter 4.0 or later which includes secured RMI connections, or implement strict network-level access controls (firewalls/VPNs) to restrict access to RMI ports if upgrade is not feasible.

Recommended fix High confidence

JMeter 3.3 or later (latest stable 5.x recommended)

  1. 1. Download Apache JMeter 3.3 or later from the official Apache JMeter website (https://jmeter.apache.org/)
  2. 2. Install the new version on all distributed test nodes (master and slave machines)
  3. 3. Ensure Java Runtime Environment (JRE/JDK) is compatible with the new JMeter version
  4. 4. Configure RMI to use SSL/TLS by setting 'server.rmi.ssl.disable=false' in jmeter.properties
  5. 5. Generate appropriate SSL certificates or use the default JMeter SSL setup for RMI communication
  6. 6. Verify the distributed test works with the secured RMI connection
Caveat May require updating test scripts if using deprecated features; ensure Java version compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jmeter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1297 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data