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