CVE-2018-1297 in the critical feed json
Missing certificate validation in Apache JMeter
published 2018-02-13 8 y ago modified 2026-06-17 4 mo ago also GHSA-7v85-6hv2-rwgw , EUVD-2022-3064
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.5%
- EPSS 11.5% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.jmeter:ApacheJMeter 4.0
Exploit prediction
11.50% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.jmeter:ApacheJMeter | <4.0 |
4.0 |
Affected products
- Apache Software Foundation Apache JMeter
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
mail-archives.apache.org
/mod_mbox/www-announce/201802.mbox/%3CCAH9fUpaNzk5am8oFe07RQ-kynCsQv54yB-uYs9bEnz7tbX-O7g%40mail.gmail.com%3E
mailing-list, web, vendor-advisory
-
bz.apache.org
/bugzilla/show_bug.cgi?id=62039
web, issue-tracking, vendor-advisory
-
lists.apache.org
/thread.html/31e0adbeca9d865ff74d0906b2248a41a1457cb54c1afbe5947df58b%40%3Cissues.jmeter.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2018-1297
advisory
-
github.com
/apache/jmeter/issues/4677
web
-
github.com
/apache/jmeter
package
-
lists.apache.org
/thread.html/31e0adbeca9d865ff74d0906b2248a41a1457cb54c1afbe5947df58b@%3Cissues.jmeter.apache.org%3E
web
Sources
- CVE List CVE-2018-1297
- GitHub Advisory GHSA-7v85-6hv2-rwgw
- NVD CVE-2018-1297
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.