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.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2018-11775 from the MITRE CVE dictionary dictionary and NIST NVD.
NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.
| CVSS3 Base Score | 6.8 |
|---|---|
| CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N |
| Attack Vector | Network |
| Attack Complexity | High |
| Privileges Required | None |
| User Interaction | Required |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity Impact | High |
| Availability Impact | None |
| Platform | Package | State |
|---|---|---|
| Red Hat Virtualization 4 | eap7-activemq-artemis | Not affected |
| Red Hat Single Sign-On 7 | activemq-artemis | Not affected |
| Red Hat JBoss Fuse Service Works 6 | activemq | Under investigation |
| Red Hat JBoss Fuse 7 | activemq | Under investigation |
| Red Hat JBoss Fuse 6 | activemq | Under investigation |
| Red Hat JBoss EAP 7 | activemq-artemis | Not affected |
| Red Hat JBoss Data Grid 7 | activemq-artemis | Not affected |
| Red Hat JBoss A-MQ 6 | activemq | Under investigation |
Vulmon