{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.jmeter:ApacheJMeter. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1287 in the wild and no public exploit code.","fix":"Upgrade org.apache.jmeter:ApacheJMeter to 4.0 or later.","what":"CVE-2018-1287 is a critical code injection vulnerability in Apache JMeter, published on 14 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1287 and fix it if it is affected.\n\nWhat it is: CVE-2018-1287 is a critical code injection vulnerability in Apache JMeter, published on 14 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1287 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.jmeter:ApacheJMeter (Maven): affected all versions; fixed in 4.0\n- org.apache.jmeter:ApacheJMeter (Maven): affected all versions; fixed in 4.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1287/ (Markdown: https://insights.sbomify.com/CVE-2018-1287/index.md)","id":"CVE-2018-1287","markdown":"https://insights.sbomify.com/CVE-2018-1287/index.md","name":"CVE-2018-1287","record":{"aliases":["DEBIAN-CVE-2018-1287","GHSA-j7j7-g4ww-pxg5","UBUNTU-CVE-2018-1287"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache JMeter","requires_auth":"none","summary":"Attackers can execute unauthorized code on JMeter servers via RMI when distributed testing is enabled with default wildcard binding.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"jmeter","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Missing certificate validation in Apache JMeter","id":"CVE-2018-1287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Improper Control of Generation of Code in Apache Kafka","id":"CVE-2018-1288"},"packages":[{"ecosystem":"Maven","fixed":["4.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.jmeter:ApacheJMeter","purl":null,"source":"GHSA-j7j7-g4ww-pxg5"},{"ecosystem":"Maven","fixed":["4.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.jmeter:ApacheJMeter","purl":"pkg:maven/org.apache.jmeter/ApacheJMeter","source":"GHSA-j7j7-g4ww-pxg5"}],"prev":{"headline":"Apache OpenMeetings may allow authenticated attacker to deny service for privileged users","id":"CVE-2018-1286"},"products":["Apache JMeter"],"published":"2018-02-14","related":[{"cvss_score":9.8,"headline":"Unauthenticated Remote Code Execution in Apache JMeter","id":"CVE-2019-0187","kev_date_added":null,"published":"2019-03-06"},{"cvss_score":9.8,"headline":"Missing certificate validation in Apache JMeter","id":"CVE-2018-1297","kev_date_added":null,"published":"2018-02-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Apache Software Foundation"]},"summary":"Attackers can execute unauthorized code on JMeter servers via RMI when distributed testing is enabled with default wildcard binding.","url":"https://insights.sbomify.com/CVE-2018-1287/"}