# CVE-2018-1297: Missing certificate validation in Apache JMeter

> Attackers can execute unauthorized code via unsecured RMI connections in Apache JMeter when using Distributed Test mode.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-1297, GHSA-7v85-6hv2-rwgw, UBUNTU-CVE-2018-1297

## What is CVE-2018-1297?

CVE-2018-1297 is a critical code injection vulnerability in Apache JMeter, published on 13 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2018-1297?

2 open source packages ship an affected version, including org.apache.jmeter:ApacheJMeter. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.jmeter:ApacheJMeter` | Maven | All versions | 4.0 |
| `org.apache.jmeter:ApacheJMeter` | Maven | All versions | 4.0 |

Products: Apache Jmeter.

## How do I fix CVE-2018-1297?

Upgrade org.apache.jmeter:ApacheJMeter to 4.0 or later.

## Is CVE-2018-1297 being exploited?

There is no known exploitation of CVE-2018-1297 in the wild and no public exploit code.

Public exploit code:

- EXP for CVE-2018-1297 (github_poc): https://github.com/Al1ex/CVE-2018-1297
- https://github.com/48484848484848/Jmeter-CVE-2018-1297- (github_poc): https://github.com/48484848484848/Jmeter-CVE-2018-1297-
- Vulhub jmeter/CVE-2018-1297: Apache JMeter RMI Deserialization RCE (CVE-2018-1297), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-jmeter-cve-2018-1297

## Other vulnerabilities in Apache JMeter

- [CVE-2019-0187](https://insights.sbomify.com/CVE-2019-0187/): Unauthenticated Remote Code Execution in Apache JMeter (critical 9.8)
- [CVE-2018-1287](https://insights.sbomify.com/CVE-2018-1287/): Missing certificate validation in Apache JMeter (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1297 and fix it if it is affected.

What it is: CVE-2018-1297 is a critical code injection vulnerability in Apache JMeter, published on 13 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1297 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.jmeter:ApacheJMeter (Maven): affected all versions; fixed in 4.0
- org.apache.jmeter:ApacheJMeter (Maven): affected all versions; fixed in 4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1297/ (Markdown: https://insights.sbomify.com/CVE-2018-1297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1297
- OSV: https://osv.dev/vulnerability/CVE-2018-1297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1297/
Summaries are generated and may contain mistakes; the official description above is the record.