Skip to content
Fencer Intel
critical 9.8

CVE-2020-11998 in the critical feed json

Remote code execution in Apache ActiveMQ

published 6y ago modified 2mo ago also BIT-activemq-2020-11998 , EUVD-2022-1236 , GHSA-wqfh-9m4g-7x6x

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
48.9%
EPSS 48.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to RMIConnectorServer, instead of the map that contains the authentication credentials, it leaves ActiveMQ open to the following attack: https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html "A remote client could create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs, at least if there is no security manager. In other words, a rogue remote client could make your Java application execute arbitrary code." Mitigation: Upgrade to Apache ActiveMQ 5.15.13

Patch / fix

  • maven org.apache.activemq:activemq-parent 5.15.13

Is CVE-2020-11998 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

48.89% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:activemq-parent
>=5.15.12, <5.15.13
5.15.13
bitnami activemq
>=5.15.12, <=5.15.12
 no fix listed

Affected products

  • n/a Apache ActiveMQ

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.