CVE-2020-13920
Published: 10 September 2020
Apache ActiveMQ uses LocateRegistry.createRegistry() to create the JMX RMI registry and binds the server to the "jmxrmi" entry. It is possible to connect to the registry without authentication and call the rebind method to rebind jmxrmi to something else. If an attacker creates another server to proxy the original, and bound that, he effectively becomes a man in the middle and is able to intercept the credentials when an user connects. Upgrade to Apache ActiveMQ 5.15.12.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
activemq Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
| focal |
Needs triage
|
|
| groovy |
Ignored
(end of life)
|
|
| hirsute |
Not vulnerable
(5.16.0-1)
|
|
| impish |
Not vulnerable
(5.16.0-1)
|
|
| jammy |
Not vulnerable
(5.16.0-1)
|
|
| kinetic |
Not vulnerable
(5.16.0-1)
|
|
| lunar |
Not vulnerable
(5.16.0-1)
|
|
| mantic |
Not vulnerable
(5.16.0-1)
|
|
| trusty |
Does not exist
|
|
| upstream |
Needs triage
|
|
| xenial |
Needs triage
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.9 |
| Attack vector | Network |
| Attack complexity | High |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |