Описание
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.
Пакеты
| Пакет | Статус | Версия исправления | Релиз | Тип |
|---|---|---|---|---|
| jakarta-jmeter | unfixed | package | ||
| jakarta-jmeter | ignored | trixie | package | |
| jakarta-jmeter | ignored | bookworm | package | |
| jakarta-jmeter | ignored | bullseye | package | |
| jakarta-jmeter | ignored | buster | package | |
| jakarta-jmeter | ignored | stretch | package | |
| jakarta-jmeter | ignored | jessie | package | |
| jakarta-jmeter | no-dsa | wheezy | package |
Примечания
https://www.openwall.com/lists/oss-security/2018/02/11/1
https://bz.apache.org/bugzilla/show_bug.cgi?id=62039
https://github.com/apache/jmeter/issues/4677
EPSS
Связанные уязвимости
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.
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.
Missing certificate validation in Apache JMeter
EPSS