Apache ActiveMQ 5.15.11 Registry LocateRegistry.createRegistry improper authentication

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Apache ActiveMQ 5.15.11. Affected by this vulnerability is the function LocateRegistry.createRegistry of the component Registry Handler. This manipulation causes improper authentication.
This vulnerability is registered as CVE-2020-13920. Remote exploitation of the attack is possible. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Apache ActiveMQ 5.15.11 (Application Server Software) and classified as problematic. Affected by this vulnerability is the function LocateRegistry.createRegistry of the component Registry Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was published 09/10/2020 (Website). It is possible to read the advisory at activemq.apache.org. This vulnerability is known as CVE-2020-13920 since 06/08/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 5.15.12 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-1253). Similar entry is available at VDB-161094. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ActiveMQ 5.15.12
Timeline
06/08/2020 🔍09/10/2020 🔍
09/11/2020 🔍
03/18/2026 🔍
Sources
Vendor: apache.orgAdvisory: activemq.apache.org
Status: Confirmed
CVE: CVE-2020-13920 (🔍)
GCVE (CVE): GCVE-0-2020-13920
GCVE (VulDB): GCVE-100-161095
EUVD: 🔍
See also: 🔍
Entry
Created: 09/11/2020 07:18Updated: 03/18/2026 13:19
Changes: 09/11/2020 07:18 (42), 09/11/2020 07:23 (18), 03/18/2026 13:19 (20)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.