jakarta-jmeter - Debian Package Tracker

general

source: jakarta-jmeter (main)
version: 2.13-5
maintainer: Debian Java Maintainers (archive) (DMD)
uploaders: Emmanuel Bourg [DMD] – Onkar Shinde [DMD]
arch: all
std-ver: 4.6.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.13-2
oldstable: 2.13-4
stable: 2.13-4
testing: 2.13-5
unstable: 2.13-5

versioned links

2.13-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

jmeter (3 bugs: 0, 2, 1, 0)
jmeter-apidoc
jmeter-ftp
jmeter-help
jmeter-http
jmeter-java
jmeter-jms
jmeter-junit
jmeter-ldap
jmeter-mail
jmeter-mongodb
jmeter-tcp

action needed

A new upstream version is available: 5.5 high

A new upstream version 5.5 is available, you should consider packaging it.

Created: 2020-06-29 Last update: 2022-12-09 19:32

3 security issues in sid high

There are 3 open security issues in sid.

3 important issues:

CVE-2018-1287: 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.
CVE-2018-1297: 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.
CVE-2019-0187: Unauthenticated RCE is possible when JMeter is used in distributed mode (-r or -R command line options). Attacker can establish a RMI connection to a jmeter-server using RemoteJMeterEngine and proceed with an attack using untrusted data deserialization. This only affect tests running in Distributed mode. Note that versions before 4.0 are not able to encrypt traffic between the nodes, nor authenticate the participating nodes so upgrade to JMeter 5.1 is also advised.

Created: 2022-07-04 Last update: 2022-08-01 13:40

3 security issues in bookworm high

There are 3 open security issues in bookworm.

3 important issues:

CVE-2018-1287: 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.
CVE-2018-1297: 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.
CVE-2019-0187: Unauthenticated RCE is possible when JMeter is used in distributed mode (-r or -R command line options). Attacker can establish a RMI connection to a jmeter-server using RemoteJMeterEngine and proceed with an attack using untrusted data deserialization. This only affect tests running in Distributed mode. Note that versions before 4.0 are not able to encrypt traffic between the nodes, nor authenticate the participating nodes so upgrade to JMeter 5.1 is also advised.

Created: 2022-07-04 Last update: 2022-08-01 13:40

lintian reports 3 errors and 13 warnings high

Lintian reports 3 errors and 13 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2021-10-13 Last update: 2022-07-30 12:14

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2022-10-10 Last update: 2022-12-09 23:01

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2018-09-11 Last update: 2022-12-09 19:34

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 2.13-6, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit da6db84d76a0e8cc655f8afb643bcb7f463663f4
Author: Andrius Merkys <merkys@debian.org>
Date:   Mon May 30 08:56:57 2022 -0400

    Update debian/changelog.

commit 4aaa13824205cd3f6872e6bd57abd8c3e86148dc
Author: Andrius Merkys <merkys@debian.org>
Date:   Mon May 30 08:56:17 2022 -0400

    Remove Onkar Shinde from the uploaders list per request. Thanks for your contributions.

Created: 2022-05-30 Last update: 2022-12-03 12:49

AppStream hints: 1 warning normal

AppStream found metadata issues for packages:

jmeter: 1 warning

You should get rid of them to provide more metadata about this software.

Created: 2020-06-01 Last update: 2020-06-01 01:13

Multiarch hinter reports 2 issue(s) low

There are issues with the multiarch metadata for this package.

jmeter-apidoc could be marked Multi-Arch: foreign
jmeter-help could be marked Multi-Arch: foreign

Created: 2016-09-14 Last update: 2022-12-10 00:01

3 low-priority security issues in bullseye low

There are 3 open security issues in bullseye.

2 issues left for the package maintainer to handle:

CVE-2018-1287: (needs triaging) 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.
CVE-2019-0187: (needs triaging) Unauthenticated RCE is possible when JMeter is used in distributed mode (-r or -R command line options). Attacker can establish a RMI connection to a jmeter-server using RemoteJMeterEngine and proceed with an attack using untrusted data deserialization. This only affect tests running in Distributed mode. Note that versions before 4.0 are not able to encrypt traffic between the nodes, nor authenticate the participating nodes so upgrade to JMeter 5.1 is also advised.

You can find information about how to handle these issues in the security team's documentation.

1 ignored issue:

CVE-2018-1297: 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.

Created: 2022-07-04 Last update: 2022-08-01 13:40

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.1 instead of 4.6.0).

Created: 2022-05-11 Last update: 2022-05-11 23:25

news

[rss feed]

[2021-09-15] jakarta-jmeter 2.13-5 MIGRATED to testing (Debian testing watch)
[2021-09-10] Accepted jakarta-jmeter 2.13-5 (source) into unstable (Markus Koschany)
[2018-08-06] jakarta-jmeter 2.13-4 MIGRATED to testing (Debian testing watch)
[2018-07-31] Accepted jakarta-jmeter 2.13-4 (source) into unstable (Emmanuel Bourg)
[2017-11-08] jakarta-jmeter REMOVED from testing (Debian testing watch)
[2017-07-29] jakarta-jmeter 2.13-3 MIGRATED to testing (Debian testing watch)
[2017-07-23] Accepted jakarta-jmeter 2.13-3 (source all) into unstable (tony mancill)
[2016-11-04] jakarta-jmeter 2.13-2 MIGRATED to testing (Debian testing watch)
[2016-10-28] Accepted jakarta-jmeter 2.13-2 (source all) into unstable (Emmanuel Bourg)
[2016-06-05] Accepted jakarta-jmeter 2.11-2+deb8u1 (source all) into proposed-updates->stable-new, proposed-updates (Emmanuel Bourg)
[2016-05-20] Accepted jakarta-jmeter 2.13-1~bpo8+1 (source all) into jessie-backports, jessie-backports (Emmanuel Bourg)
[2016-04-05] jakarta-jmeter 2.13-1 MIGRATED to testing (Debian testing watch)
[2016-03-30] Accepted jakarta-jmeter 2.13-1 (source all) into unstable (Emmanuel Bourg)
[2015-12-12] jakarta-jmeter 2.11-5 MIGRATED to testing (Debian testing watch)
[2015-12-06] Accepted jakarta-jmeter 2.11-5 (source all) into unstable (Markus Koschany)
[2015-11-03] jakarta-jmeter 2.11-4 MIGRATED to testing (Britney)
[2015-10-28] Accepted jakarta-jmeter 2.11-4 (source) into unstable (Markus Koschany)
[2015-07-22] jakarta-jmeter 2.11-3 MIGRATED to testing (Britney)
[2015-07-16] Accepted jakarta-jmeter 2.11-3 (source all) into unstable (Emmanuel Bourg)
[2014-09-24] jakarta-jmeter 2.11-2 MIGRATED to testing (Britney)
[2014-09-18] Accepted jakarta-jmeter 2.11-2 (source all) into unstable (Emmanuel Bourg)
[2014-07-23] Accepted jakarta-jmeter 2.11-1 (source all) (Emmanuel Bourg) (signed by: tony mancill)
[2014-04-22] jakarta-jmeter 2.8-2 MIGRATED to testing (Debian testing watch)
[2014-04-11] Accepted jakarta-jmeter 2.8-2 (source all) (Emmanuel Bourg)
[2013-07-16] jakarta-jmeter 2.8-1 MIGRATED to testing (Debian testing watch)
[2013-07-05] Accepted jakarta-jmeter 2.8-1 (source all) (Emmanuel Bourg)
[2013-07-03] Accepted jakarta-jmeter 2.5.1-2 (source all) (Emmanuel Bourg)
[2012-05-22] jakarta-jmeter 2.5.1-1 MIGRATED to testing (Debian testing watch)
[2012-05-12] Accepted jakarta-jmeter 2.5.1-1 (source all) (Onkar Shinde) (signed by: tony mancill)
[2012-05-03] jakarta-jmeter 2.4-3 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 8
RC: 0
I&N: 6
M&W: 2
F&P: 0
patch: 1

links

homepage
lintian (3, 13)
buildd: logs, reproducibility
popcon
browse source code
edit tags
other distros
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.13-5
3 bugs (1 patch)