Debian Package Tracker
Register | Log in
Subscribe

jakarta-jmeter

Choose email to subscribe with

general
  • source: jakarta-jmeter (main)
  • version: 2.13-6.1
  • maintainer: Debian Java Maintainers (archive) (DMD)
  • uploaders: Onkar Shinde [DMD] – Emmanuel Bourg [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-4
  • oldstable: 2.13-5
  • stable: 2.13-5
  • testing: 2.13-6.1
  • unstable: 2.13-6.1
versioned links
  • 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]
  • 2.13-6.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • jmeter (4 bugs: 0, 3, 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.6.3 high
A new upstream version 5.6.3 is available, you should consider packaging it.
Created: 2025-11-27 Last update: 2026-04-28 21:31
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: 2026-04-28 19:02
3 security issues in forky high

There are 3 open security issues in forky.

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: 2025-08-09 Last update: 2026-04-28 19:02
lintian reports 18 warnings high
Lintian reports 18 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2021-10-13 Last update: 2026-04-21 10:31
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.
Created: 2022-05-30 Last update: 2026-04-21 03:30
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: 2025-01-25 Last update: 2026-04-28 23:33
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: 2026-04-29 00:30
3 low-priority security issues in trixie low

There are 3 open security issues in trixie.

1 issue left for the package maintainer to handle:
  • 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 this issue in the security team's documentation.

2 ignored 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.
Created: 2025-08-09 Last update: 2026-04-28 19:02
3 low-priority security issues in bookworm low

There are 3 open security issues in bookworm.

1 issue left for the package maintainer to handle:
  • 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 this issue in the security team's documentation.

2 ignored 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.
Created: 2023-06-10 Last update: 2026-04-28 19:02
debian/patches: 6 patches to forward upstream low

Among the 13 debian patches available in version 2.13-6.1 of the package, we noticed the following issues:

  • 6 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2023-02-26 Last update: 2026-04-21 08:30
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.0).
Created: 2022-05-11 Last update: 2026-04-21 03:20
news
[rss feed]
  • [2026-04-26] jakarta-jmeter 2.13-6.1 MIGRATED to testing (Debian testing watch)
  • [2026-04-20] Accepted jakarta-jmeter 2.13-6.1 (source) into unstable (Vagrant Cascadian)
  • [2025-01-25] jakarta-jmeter 2.13-5 MIGRATED to testing (Debian testing watch)
  • [2024-09-14] jakarta-jmeter REMOVED from testing (Debian testing watch)
  • [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)
  • 1
  • 2
bugs [bug history graph]
  • all: 8
  • RC: 0
  • I&N: 6
  • M&W: 2
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 18)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.13-5build1
  • 3 bugs (1 patch)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing