activemq: ActiveMQ Client Missing TLS Hostname Verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache ActiveMQ | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Fuse 7.5.0 | |||
| activemq | cpe:/a:redhat:jboss_fuse:7 | RHSA-2019:3892 | 2019-11-14T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2583-1 | activemq security update |
EUVD |
EUVD-2018-0638 | TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default. |
Github GHSA |
GHSA-m9w8-v359-9ffr | Improper Certificate Validation in Apache activemq-client |
Ubuntu USN |
USN-6910-1 | Apache ActiveMQ vulnerabilities |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 7.0% (6.959% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.