CVE-2018-1297: Critical severity apache jmeter vulnerability

Published Feb 13, 2018
·
Updated

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.

Affected Software

63 affected components
Apache JMeter=2.1
Apache JMeter=2.2
Apache JMeter=2.3
Apache JMeter=2.3.1
Apache JMeter=2.3.2
Apache JMeter=2.3.3
Apache JMeter=2.3.3-rc1
Apache JMeter=2.3.3-rc2
Apache JMeter=2.3.4
Apache JMeter=2.3.4-rc1
Apache JMeter=2.3.4-rc2
Apache JMeter=2.3.4-rc3
Apache JMeter=2.4
Apache JMeter=2.5
Apache JMeter=2.5-rc1
Apache JMeter=2.5-rc2
Apache JMeter=2.5-rc3
Apache JMeter=2.5.1
Apache JMeter=2.5.1-rc1
Apache JMeter=2.5.1-rc2
Apache JMeter=2.5.1-rc3
Apache JMeter=2.6
Apache JMeter=2.6-rc1
Apache JMeter=2.6-rc2
Apache JMeter=2.7
Apache JMeter=2.7-rc1
Apache JMeter=2.7-rc2
Apache JMeter=2.7-rc3
Apache JMeter=2.8
Apache JMeter=2.8-rc1
Apache JMeter=2.8-rc2
Apache JMeter=2.9
Apache JMeter=2.9-rc1
Apache JMeter=2.9-rc2
Apache JMeter=2.9-rc3
Apache JMeter=2.10-rc1
Apache JMeter=2.10-rc2
Apache JMeter=2.11
Apache JMeter=2.11-rc1
Apache JMeter=2.11-rc2
Apache JMeter=2.12
Apache JMeter=2.12-rc1
Apache JMeter=2.12-rc2
Apache JMeter=2.13
Apache JMeter=2.13-rc1
Apache JMeter=2.13-rc2
Apache JMeter=3.0
Apache JMeter=3.0-rc1
Apache JMeter=3.0-rc2
Apache JMeter=3.0-rc3
Apache JMeter=3.0-rc4
Apache JMeter=3.0-rc5
Apache JMeter=3.1
Apache JMeter=3.1-rc1
Apache JMeter=3.1-rc2
Apache JMeter=3.1-rc3
Apache JMeter=3.1-rc4
Apache JMeter=3.2
Apache JMeter=3.2-rc1
Apache JMeter=3.2-rc2
Apache JMeter=3.2-rc3
Apache JMeter=3.3
Apache JMeter=3.3-rc1

Event History

Feb 13, 2018
CVE Published
via MITRE·12:00 PM
Data Sourced
via MITRE·12:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-1297?

CVE-2018-1297 is classified as a medium severity vulnerability due to the potential for unauthorized access and remote code execution.

2

How do I fix CVE-2018-1297?

To remediate CVE-2018-1297, upgrade to a fixed version of Apache JMeter that resolves the unsecured RMI connection issue.

3

What versions of Apache JMeter are affected by CVE-2018-1297?

CVE-2018-1297 affects Apache JMeter versions 2.1 through 3.3, including release candidates.

4

What kind of attack can exploit CVE-2018-1297?

CVE-2018-1297 can be exploited by an attacker who gains access to the unsecured RMI connection, potentially allowing them to execute arbitrary code.

5

Is it safe to use Apache JMeter if running a vulnerable version related to CVE-2018-1297?

Using an affected version of Apache JMeter poses significant security risks, and it is advised to update to a secure version immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203