Most recent entries from all https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 21:37:32 +0000 cnvd-2018-03761 https://cve.radiocsirt.org/vuln/cnvd-2018-03761 cnvd-2018-03761 https://cve.radiocsirt.org/vuln/cnvd-2018-03761 EUVD-2026-183050 https://cve.radiocsirt.org/vuln/euvd-2026-183050 EUVD-2026-183050 https://cve.radiocsirt.org/vuln/euvd-2026-183050 fkie_cve-2018-1287 https://cve.radiocsirt.org/vuln/fkie_cve-2018-1287 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-1287 GHSA-j7j7-g4ww-pxg5 — Missing certificate validation in Apache JMeter https://cve.radiocsirt.org/vuln/ghsa-j7j7-g4ww-pxg5 <p><strong>Affected:</strong> Maven: org.apache.jmeter:ApacheJMeter</p> <p>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. This only affect those running in Distributed mode.</p> <p>In distributed mode, JMeter makes an architectural assumption that it is operating on a &#39;safe&#39; network. i.e. everyone with access to the network is considered trusted.</p> <p><strong>Affected:</strong> Maven: org.apache.jmeter:ApacheJMeter</p> <p>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. This only affect those running in Distributed mode.</p> <p>In distributed mode, JMeter makes an architectural assumption that it is operating on a &#39;safe&#39; network. i.e. everyone with access to the network is considered trusted.</p> https://cve.radiocsirt.org/vuln/ghsa-j7j7-g4ww-pxg5 gsd-2018-1287 https://cve.radiocsirt.org/vuln/gsd-2018-1287 gsd-2018-1287 https://cve.radiocsirt.org/vuln/gsd-2018-1287 UBUNTU-CVE-2018-1287 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-1287 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: jakarta-jmeter, Ubuntu:18.04:LTS: jakarta-jmeter, Ubuntu:20.04:LTS: jakarta-jmeter, Ubuntu:22.04:LTS: jakarta-jmeter, Ubuntu:24.04:LTS: jakarta-jmeter, Ubuntu:25.10: jakarta-jmeter, Ubuntu:26.04:LTS: jakarta-jmeter</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: jakarta-jmeter, Ubuntu:18.04:LTS: jakarta-jmeter, Ubuntu:20.04:LTS: jakarta-jmeter, Ubuntu:22.04:LTS: jakarta-jmeter, Ubuntu:24.04:LTS: jakarta-jmeter, Ubuntu:25.10: jakarta-jmeter, Ubuntu:26.04:LTS: jakarta-jmeter</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-1287